Hi! 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?
Arne -- [--- PGP key FD05BED7 --- http://www.root42.de/ ---]
pgprlQfybhibJ.pgp
Description: PGP signature
