In article <[EMAIL PROTECTED]> you wrote: > the pid file exists and the program is already running, it sends a > SIGUSR1 and exits with status 1.
This is the normal way you do pid file locking, beside you use kill(pid, 0) instead of usr1. More advanced code will check the inode of the binary or something, however this has some other disadvantages (on upgrade). > It is obvious that the way the program is behaving the bug report is > they it is programmed to behave. I would like to know if there is a > better way to handle this. If you want to keep USR1 then you have to ignore it. Gruss Bernd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
