Return to BSD News archive
Xref: sserve comp.unix.bsd.freebsd.misc:3576 comp.unix.programmer:27293 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!news.primenet.com!jrugen From: jrugen@primenet.com (Jeff Rugen) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.programmer Subject: xterm & SIGINT Date: 20 Jul 1995 15:14:28 GMT Organization: PrimeNet Lines: 25 Message-ID: <3ulrsl$jf7@nnrp1.primenet.com> NNTP-Posting-Host: usr1.primenet.com X-Newsreader: TIN [version 1.2 PL2] I have no idea where else to post this question... its not BSD specific exactly... more so xterm, but since that is common in most *nixes I've seen... I'm writing a program that has a little command-line interface. One command will cause the program to fork() and exec an xterm, running tail in the new xterm to continuously display a file that's updating. My main program can execute scripts, and I'm catching SIGINT to abort execution of the script. This works fine - when I hit ^C, the script aborts. Unfortunately, the xterm running tail also gets killed. This isn't a terrible problem, but its an annoyance. I run signal(SIGINT, SIG_IGN) after the fork (immediatly before the execl to start the xterm) but I guess the xterm resets the signal to default handling. How can I prevent the xterm from catching the SIGINT? Brousing through the man page shows something that may work - one of the x resources, but it also may only affect one of the menus. Thanks for any help. Please email me any responses, as I don't regularly read this newsgroup. -- ------------------------------------------------------------------------------- Jeff Rugen __ __ ____ ___ ___ ____ jrugen@primenet.com /__)/__) / / / / /_ /\ / /_ / Motorola GSTG / / \ / / / / /__ / \/ /___ / -------------------------------------------------------------------------------