On Fri, Sep 28, 2012 at 9:47 PM, Kok, Auke-jan H <[email protected]> wrote: > On Fri, Sep 28, 2012 at 4:23 AM, Peeters Simon <[email protected]> > wrote: >> 2012/9/28 Peter Lemenkov <[email protected]>: >>> Hello All! >> Hello >> >>> First question - is this a correct way to run systemd --user? I saw a >>> "[email protected] script" but it does requires root permission to run. >> this is afaik a correct way as long as a single user does not have >> multiple sessions. >> >>> Second question - I've lost all /etc/profile stuff which was set up >>> somehow in the depths of Xorg-related script's swamp. I'd like to run >>> it (as well as some other shell scripts) and borrow its envvars (at >>> least for some applications) - is it possible? >> >> systemd currently does not parse /etc/profile (and never will?) > > it shouldn't - you can't just "parse" it - you have to basically eval > it in a full shell, and this is frankly out of fashion.
Unfortunately, all other options (EnvironmentFile and pam_env) are just too limited – none of them support even plain nesting of variables (as in PATH=$HOME/bin:$PATH or XDG_CONFIG_HOME=$HOME/.config). I try to keep my ~/.environ clean of shell logic (http://git.io/S0M_Sg), but I still cannot see myself giving up `MAKEFLAGS=-j$(nproc)` or `source ~/.environ-$HOSTNAME`... Not to mention that many packages install /etc/profile.d/ scriptlets to set envvars the program depends on (JAVA_HOME, MOZ_PLUGIN_PATH, and even LANG – which has to be set from profile because [email protected] unsets it.) -- Mantas Mikulėnas _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
