Hi folks, After grabbing the source packages for lightdm and lightdm-gtk-greeter from Debian experimental and applying some patches to lightdm to fix the language selector, I now have it working on a Debian wheezy test system. However, before it's ready for production, I need it to run a user login script and a user logout script. Unfortunately, it seems lightdm is only capable of running these scripts as root (via session-setup-script and session-cleanup-script), which makes things a little more complicated, instead of as the user logging in or out. My question is, what is the most reliable way to determine the user account name involved when these login and logout scripts are run? Thanks, Jaap
* Jaap Winius <jwinius at umrk.nl> [2012-12-21 05:20]:> Hi folks, > > After grabbing the source packages for lightdm and lightdm-gtk-greeter > from Debian experimental and applying some patches to lightdm to fix the > language selector, I now have it working on a Debian wheezy test system. > > However, before it's ready for production, I need it to run a user login > script and a user logout script. Unfortunately, it seems lightdm is only > capable of running these scripts as root (via session-setup-script and > session-cleanup-script), which makes things a little more complicated, > instead of as the user logging in or out. > > My question is, what is the most reliable way to determine the user > account name involved when these login and logout scripts are run?Both scripts are called with USER/LOGNAME/HOME set, however they are not intended for that. It is probably more appropriate to hook these scripts into the session wrapper and/or your window manager/desktop environment. -- Guido Berhoerster