Two more things you might find useful to know:
firstly, note that the command Kill (1) does not send SIGKILL unless you
specify it to do so (you can choose which signal it sends the process), the
command kill <pid> will send a SIGTERM signal, which you can (and should)
handle for clean termination. Only a mean admin (or one that is tired of
your program not exiting when it is told to) will use a weapon of mass
destruction like SIGKILL on it.
The other piece of trivia that you should be informed of if by chance
you are not already, is that while SIGHUP officially indicates that the
terminal line your program is attached to "hanged up" (and therefore there
is no point running any longer), it has another use for daemon (typically
server) processes: as they are not attached to any terminal, server daemons
usually take a SIGHUP signal as an order to restart/re-read configuration.
third out of two: Stevens is the ultimate reference on this, and it
definitely deserves a spot on your bookshelf if you are dealing with these
things - I think I own at least two copies of it if not more :-)
-Federico
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish
Muad'Dib of Caladan (Federico L. Lucifredi)- [EMAIL PROTECTED],
http://www.lucifredi.com
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
