Re: Gnome logout script

[Sean Atkinson <sean netproject com>]

> > Sure, unless there's some reason I don't understand that some of its
> > processes choose to hang around.  However that's a bigger problem for
> > the longer term.  Also there are other reasons to want logout scripts
> > and tidy up the user's environment, so I think it's worth looking into.
> > 
> evolution-alarm-notify has to be kept around, for calendar alarms, and
> since it uses the wombat for the calendar, it also keeps
> evolution-wombat around. So, those 2 processes are saved in the session,
> which is what they are supposed to do.
> 
> There is a bug in Ximian's bugzilla about making it exit if there are no
> alarms. But if so, we need a way to restart the alarm daemon at some
> interval in the future to check for new alarms.

Looking into the processes left after a clean logout, I find
evolution-wombat remains without any alarm (I didn't set any). 
Presumably as a result of this bonobo-activation-server and gconfd-2
also remain.  Previously I remember seeing oafd too.

The file locks left by gconfd-2 are probably the biggest problem since
they prevent login from another machine sharing the same /home, but I'm
looking into that separately.

-- 
Sean Atkinson <sean netproject com>
Netproject