On 5/20/05, Arne Schmitz <[EMAIL PROTECTED]> wrote: > What is bugging me for months is: The detection whether an instance of LICQ is > already running is a bit buggy. The problem ist, that KDE almost always > leaves a stale lockfile. And it sometimes happen that there is some process > (not LICQ) running with the same PID, when LICQ will be started on the next > login. So LICQ aborts. I think one of the problems is, that KDE doesn't wait > for LICQ to finish -- could this probably be worked around by using session > management? Or does LICQ do this already?
The current method creates a file with the PID of Licq in it. When Licq is cleanly shutdown, this file gets erased. If Licq is closed uncleanly, the file will remain there and if there is another process with the same PID, Licq will terminate itself. How do you close Licq? Jon ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id344&op=click _______________________________________________ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
