I think you may have misunderstood this bug report.
As I understand it the code is intended to check for a lock. If the lock is
there and the old pid still exists the new process should die. Otherwise
remove the old lock and continue.
The problem is that the KILL(2) call is used to check to see if a process
exists at the specified PID. The default action for SIGUSR1 is to kill the
targeted process. Thus the original process dies, and the new process exits.
The propper thing to do is to use kill(pid,0), which just checks if a
process exists with that pid without actually signaling it. This is standard
behavoir, for this type of thing.
The bug is not that the second hotkey fails to start, but rather that the
attempt to start the seccond hotkey kills the first and then the second
exits.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
