Catching ^C and ^Z
Stanley Friesen
sarima at tdatirv.UUCP
Thu Sep 6 01:47:02 AEST 1990
In article <Sep.5.01.20.23.1990.18603 at sparky.rutgers.edu> gaynor at sparky.rutgers.edu (Silver) writes:
>weisen at 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.
Except that this is totally irrelevant. SIGKILL and SIGSTOP *cannot* be
generated by any keystroke sequence on a terminal! They may *only* be generated
by software means, such as kill(1) or kill(2). In addition only the owner of
the process and the superuser are allowed to do this, so they do *not* effect
the security of a lock program.
---------------------------------
uunet!tdatirv!sarima (Stanley Friesen)
(Teradata Corporation)
-
-
-
-
-
-
More information about the Comp.lang.c
mailing list