[14:26] <Nikratio> What is the best way to give an upstart job access to the environment variables defined in /etc/environment? Unfortunately upstart does not seem to run pam_env.so, and explicitly sourcing /etc/environment in a script block requires to add additional "export" declarations into the script for all the variables (which is nasty, because I then have to manually  keep the upstart config and /etc/environment in sync)
[14:30] <ion> PAM support is in TODO.
[14:30] <ion> For now, use su.
[14:31] <Nikratio> A plain "su [user] -c command" creates a su:session log entry in auth.log, but the variables are still not defined.
[14:32] <Nikratio> Does it have to be a login-su?
[14:32] <ion> I don’t know offhand, you’ll have to test it.
[14:33] <Nikratio> Actually I did test it, and with su -l it works. I was hoping to extract some info on why that's necessary. But I guess I'm in the wrong room for that ;-)