Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!umich!sharkey!msuinfo!netnews.upenn.edu!weisen@eniac.seas.upenn.edu From: weisen@eniac.seas.upenn.edu (Neil Weisenfeld) Newsgroups: comp.lang.c Subject: Re: Catching ^C and ^Z Message-ID: <29335@netnews.upenn.edu> Date: 9 Sep 90 18:26:13 GMT References: <439@mole-end.UUCP> Sender: news@netnews.upenn.edu Reply-To: weisen@eniac.seas.upenn.edu (Neil Weisenfeld) Organization: University of Pennsylvania Lines: 36 In-reply-to: mat@mole-end.UUCP (Mark A Terribile) In article <439@mole-end.UUCP>, mat@mole-end (Mark A Terribile) writes: >> > [I wanna write a lockscreen.] > >> weisen@eniac.seas.upenn.edu: >> > Under BSD, you should be able to do something like: >> > signal(SIGINT,SIG_IGN); >> > signal(SIGQUIT,SIG_IGN); >> > to IGNore the signals. > >> SunOS signal(3): >> > SIGKILL 9 kill (cannot be caught, blocked, or ignored) >> > SIGSTOP 17 stop (cannot be caught, blocked, or ignored) > >> Therein lies the incentive to capture the characters before a shell can see >> them. > [stuff deleted about ^C not generating SIGINT and ^Z not generating SIGSTOP] How does my name keep ending up at the top of a message with a whole bunch of leading >>>>'s? What happened to the names of the people who actually wrote that stuff? The only part of this mess that was written by me is the part about SIGINT and SIGQUIT. Also, according to the man page for SIGNAL(3), SIGSTOP is not generated from the keyboard, SIGTSTP is! Neil P.S. -- Please stop misquoting me: The text after the SunOS signal(3) is NOT WHAT I PUT THERE...arrrgh! -- _____________________________________________________________________________ ( ) _ ( ) Neil Weisenfeld | 3900 Chestnut St. ( )(_)_ ( ) Computer Science and Engineering | Apt. 233 ( ) (_)_ ( ) School of Engineering and Applied Science | Philadelphia, PA