[08:45] <afournier1> hello
[08:45] <afournier1> is it possible to define an env variable globally ? 
[08:56] <jodh> afournier1: what's your use case?
[08:57] <afournier1> i'd like to define LANG globally
[08:57] <afournier1> or TERM, or TZ
[08:57] <afournier1> and i only use upstart, no sysvinit scripts
[08:59] <jodh> afournier1: well, for Session Inits you can now make use of 'initctl set-env', however, that won't work for system jobs (although I'm wondering about enabling that for Upstart 1.9).
[09:00] <afournier1> that would be nice if it was possible to define this at upstart startup (pid 1) with a configuration file for example
[09:01] <afournier1> so all children process have a configurable and some how standardized environment
[09:01] <afournier1> then a job can rewrite/add variables as needed
[09:03] <jodh> afournier1: please can you raise a bug so we can consider this for Upstart 1.9. I am very wary of enabling 'initctl set-env --global' for PID 1 as that could allow a job to DoS the system.
[09:04] <afournier1> at the same time may not be a good idea when changing a variable
[09:04] <afournier1> yes
[09:06] <afournier1> i will check my process graph, maybe i can add insert a job at the begining (just after startup) 
[09:06] <afournier1> between mountall and startup, would this work ?
[09:12] <jodh> afournier1: you could create a "start on starting mountall" job to inject vars into mountall and all job environments that start on mountall, yes.
[09:47] <afournier1> jodh: but it would not inject those vars to the jobs that start on the jobs that start on mountall, that's it ?
=== Md_ is now known as Md