Randy McMurchy wrote: > Hi all, >
As said by Jürg, apart from the systemwide daemon, for every user a sessiondaemon has to started too I understand. Now his sollution to this is an extra script (dbus) in the directory /etc/X11/xinit/xinitrc.d. (I do not know this directory, it's like the profile.d dir for bash I assume) Now I've been working on a construction to execute scripts when a user logs in and logs out. It's based on the pammodule pam_script, which is part of the sessionpart of the login (and kdm) service. I've written a script about this: (restoresettingsaslogin) "Storing and retrieving settings per user at login and logout using PAM." This is only an example. I'm working on an simular construction using FUSE, fusesmb and pam_storepw to browse the network. In this case a script for a user has to be executed by/for the user logging in (fusesmb $mountpoint). The session part of PAM is ideal for this IMHO. Isn't it an idea to put a dbus.sh script there. Then the script is executed at login no matter what you're going to do, console(bash/sh...) or graphical(kdm/gdm/xdm). But with some configuration it's possible to only start this session-daemon when starting a graphical session. And everything can be terminated properly when logging out, when an other script is executed. Stef Bon -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
