On Mon, Aug 29, 2005 at 10:43:53PM -0400, Uri Guttman wrote: > SIGKILL isn't overkill, but just wrong. as several of us have mentioned, > you can't ever catch KILL as it is defined to be uncatchable. so setting > a handler for it is useless code.
While you can't catch SIGKILL, you might want to notice when it has happened. Obviously you can't do that in the process being KILLed, but you could have your program notice and clean up the next time it is run. RDBMSes do this sort of thing. -- David Cantrell | Official London Perl Mongers Bad Influence Hail Caesar! Those about to vi ^[ you! _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
