in reply to Perl scripts quit unexpectedly

Some solutions, from best to worst:

1) Why aren't you using flock? Create the lockfile if it doesn't exist, then flock it. The lock will be cleared if the process exits by any means. Don't worry about deleting the lockfile (but you can if you want).

2) Another way is to store the locker's pid in the lockfile. To check if the lock is active check for both the presence of the lockfile and the presense of the process mentioned therein. If the process isn't running, the lock must be stale.

3) Use END. This will work if the script dies, but it won't work if the script is killed.

{ my $lock = ...; my $on_exit = sub { releaseLock($lock); }; eval 'END { $on_exit->() }'; }

You shouldn't modify the END line at all, lest you risk introducing bugs and security problems. Make your changes to on_exit instead.

Replies are listed 'Best First'.
Re^2: Perl scripts quit unexpectedly
by lpoht (Sexton) on Jul 27, 2005 at 22:43 UTC
    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
      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.