Hi,
On Thu, 2008-01-03 at 20:10 -0500, David Zeuthen wrote:
Notably, 00-ck-xinit-session.sh will take care of problem 2. The way
it
does this is because of the way that ConsoleKit works. It basically will
just kill all the processes where the uid and the environment variable
XDG_SESSION_COOKIE matches. First it tries SIGTERM. Then after a few
seconds, it moves on to SIGKILL (e.g. -9).
(of course, any process can unset XDG_SESSION_COOKIE and then fork and
that way linger on. But no sane process would do that unless it's
hostile.)
Not in the least, there are programs which are supposed to stay running
even when you log out -- screen, vncserver, nohup'ed processes etc. Mind
that non-desktop oriented projects might not be that inclined to work
around the "desktop strangeness du jour" (background processes being
killed when logging out would count as such).
On Thu, 2008-01-03 at 20:39 -0500, Havoc Pennington wrote:
This may be obvious, but the "correct" solution is supposed
to be that
apps should connect to either the X server or the session message bus
and they should exit when the X server or message bus does. (Both Xlib
and libdbus exit on disconnect by default for this reason.)
This would solve the problem above more cleanly.
Nils
--
Nils Philippsen / Red Hat / nphilipp(a)redhat.com
"Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011