On Mon, 2006-10-16 at 10:50 +0200, Thomas Bächler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jan de Groot schrieb:
> >> I am using gnome 2.16 (sorry for not meantioning that) from testing and
> >> it doesn't stop dbus-daemon at logout.
> >
> > dbus only stops when all processes that have been launched from either
> > dbus or the gnome-session process have been stopped. If some process
> > thinks it should keep running, so will dbus in that case.
>
> For my personal start scripts I use a trick to prevent more than one
> dbus session to be started. It goes like this:
>
> is_running() {
> for pid in $(pidof "$1"); do
> if kill -0 $pid 2>/dev/null; then
> return 0
> fi
> done
> return 1
> }
> if ! is_running dbus-daemon; then
> dbus-launch --sh-syntax > $HOME/.dbus-env
> fi
> source $HOME/.dbus-env
>
> I wonder why gnome doesn't have a mechanism like this. Having multiple
> dbus sessions for one user doesn't make much sense to me.
Having dbus launched outside of X makes it fail. gnome-session launches
its own dbus sessionbus when no bus is available. Before launching, it
makes sure the gnome-keyring-daemon environment variables, the session
manager variables and the DISPLAY variables are set, then the dbus
daemon is launched. If you start your own, weird things will happen
(evolution losing its password storage ability when launched via
keyboard hotkeys, gnome-settings-daemon doing weird things, etc).
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
