Re: [systemd-devel] $PWD=/ in systemd --user
On Tue, 03.07.12 14:26, Kok, Auke-jan H (auke-jan.h@intel.com) wrote: On Tue, Jul 3, 2012 at 11:10 AM, Léo Gillot-Lamure leo.gil...@navaati.net wrote: I'm running a user session using systemd --user and my PWD in the session (visible, for example, when launching a xterm) is / instead of $HOME as one would expect. That's a bit annoying. I tried to wrap systemd --user in a script doing cd $HOME before exec'ing it, but it doesn't change anything. Have you guys using the user session noticed the same thing ? yes. Basically systemd --user doesn't do the sane default stuff that you would expect. I've been thinking of a way to solve the issue, but it's not clear to me what the right solution is: - write a wrapper that wraps around systemd --user. This could handle login management as well and talk to logind. - write or use pam modules to do these bits for us, and just let /etc/pam.d/login(?) catch it. I'd be happy to take a patch that makes WorkingDirectory= default to getenv(HOME) for all services, if we are running as user instance! Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] $PWD=/ in systemd --user
Hi. I'm running a user session using systemd --user and my PWD in the session (visible, for example, when launching a xterm) is / instead of $HOME as one would expect. That's a bit annoying. I tried to wrap systemd --user in a script doing cd $HOME before exec'ing it, but it doesn't change anything. Have you guys using the user session noticed the same thing ? Regards, Léo Gillot-Lamure. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] $PWD=/ in systemd --user
On Tue, Jul 3, 2012 at 11:10 AM, Léo Gillot-Lamure leo.gil...@navaati.net wrote: I'm running a user session using systemd --user and my PWD in the session (visible, for example, when launching a xterm) is / instead of $HOME as one would expect. That's a bit annoying. I tried to wrap systemd --user in a script doing cd $HOME before exec'ing it, but it doesn't change anything. Have you guys using the user session noticed the same thing ? yes. Basically systemd --user doesn't do the sane default stuff that you would expect. I've been thinking of a way to solve the issue, but it's not clear to me what the right solution is: - write a wrapper that wraps around systemd --user. This could handle login management as well and talk to logind. - write or use pam modules to do these bits for us, and just let /etc/pam.d/login(?) catch it. - ??? Auke ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
