[14:13] is this channel logged? [14:13] im looking for an answer i got last week [14:20] hvgotcodes: http://irclogs.ubuntu.com/ [14:32] soren: thanx [14:32] sure [14:52] soren: i cant find it -- the question last week was basically how to read env variables out of /etc/environment and make them available for the process that upstart is managing. [14:53] the upstart conf i had is here [14:53] https://gist.github.com/ef3ff41c2928db636917 [14:53] i think i just need to add some script sections to read the environment [15:12] soren: i found the pastebin with the answer i got on this forum -- problem is when i try it the git_repo variable is not seen from within the process [15:12] http://paste.ubuntu.com/600007/ [15:29] hvgotcodes: sudo cleans up the environment, you'll need to add the -E option to sudo [15:30] (I should say: it cleans up the environment with a default Ubuntu sudoers config) [15:36] and you might also have to add an option in sudoers to allow this [15:37] JanC: you are saying just add a -E? [15:37] is there a better way to be doing this? [15:38] I haven't tested if just -E is enough; maybe you'll need to change sudoers [15:39] JanC: what do you mean by it 'cleans up the environment'? I thought that /etc/environment was always available no matter what [15:40] there is no -E option for sudo [15:40] at least in the man page [15:41] oh yeah it is there [15:43] hmm why do i get stop: Unable to connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory when i try to do service theservice stop? [15:44] i wonder if it would be better to have a wrapper script to launch the process, and source the environment in there [21:02] would a post on the upstart-devel list about my vserver + blocking upstart problems be appropriate? [21:03] I'm not sure how strict the list is about separating user support from development [21:22] radix: user questions are welcome AFAIK (there isn't that much traffic) [23:00] okie doke