The application cannot 'keep running' in the sense of presenting its GUI, but it can still consume other resources such as memory, CPU, and network...
Mozilla and OpenOffice are excellent examples of apps with a fondness for this. Often they'll mostly terminate, but not completely - usually one thread remains spinning, preventing the removal of the lock file.
Both apps signal a running instance if found rather then starting a new intance, so such a 'hung' instance must be killed manually to get the app working again for that user.
Both apps can be left in this state after an app crash and subsequent Xkill, or by the unexpected exit of the X server.
A mechanism to guarantee the death of such applications when their X connection is closed would be immensely handy. Currently I have a login script that kills any mozilla & soffice instances under the user's ID, and a 'watchdog' in cron that looks for and kills 'hung' mozilla/soffice instances every minute. It's a right pain.
The real fix, of course, is to code those applications properly, but there will always be broken applications out there.
Craig Ringer
_______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
