in reply to Re: Perl scripts quit unexpectedly
in thread Perl scripts quit unexpectedly

Thanks for the tips. I have updated the code to use flock - a much smarter method. I was thinking that an END block may be a good way to debug how this script is exiting. However, since it's not a function call I am not sure what useful information I can print out in the END block.

Will an END block run if the process receives a SIGKILL, SIGSTOP, or SIGQUIT? If so, is there any way to log the recipt of these signals since I can't create a handler for the first two. Thanks

Replies are listed 'Best First'.
Re^3: Perl scripts quit unexpectedly
by ikegami (Patriarch) on Jul 27, 2005 at 22:52 UTC
    As I understand things, SIGKILL is never received by the application, so you wouldn't be able to log that one. The whole idea behind that signal is to kill non-responsive processes, a task ill-suited for the process being killed. I'm not familiar with the other signals you mentioned.