Justin Pryzby wrote:
What is the expected (desired?) behaviour? Check the indicated PID, and if it is not a firefox process, remove the lock automatically? (Could be implemented on linux by checking /proc/$pid/exe symlink).
That would be ideal, although the current lock does not seem to hold the pid anywhere (it's a broken symbolic link to a port number?).
A workaround would be to delete the lock on system startup; at least then when you reboot it will be fixed (and the system crash case that I mentioned would work properly).
-jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
