[09:29] So, no update here, huh? [09:30] I get the same results when I export HOME=/opt/logstash within script, so I'm assuming something is going wrong :-\ [17:51] jMCg: looking now [17:53] jMCg: export in upstart jobs is for the events only. All env's are "exported" to the scripts/processes that are run in pre/post-stop/start and the main process [17:54] jMCg: http://paste.ubuntu.com/1121877/ [17:54] jMCg: results in Jul 31 10:52:18 clint-MacBookPro test: HOME=/home/foo [18:09] SpamapS: so that should work :-S [18:12] jMCg: yes it should. Are you certain java is really java, and not some shell script that sources an env file? [18:27] SpamapS: http://sprunge.us/bNfB [18:29] jMCg: ok well then HOME should be set :) [18:39] \but the progra, is still spitting out millions of errors, which relate to HOME not being set [18:57] (Which is kind of counter productive, because it's supposed to collect and index logs ;) [19:23] I have a script that runs as a foreach loop over a long list, and executes a command on each one. is it kosher to add the foreach and all between script and end script? or should I haveit pulled out into a separate file [19:24] (I know I *could* do it, but best practices anda ll..) [19:26] gchristensen: what, exactly, does it do? [19:28] it iterates over a list of 500+ clients and triggers an event in a queue. the "general" idea is we want this system to basically continue running forever, so at the end of the list it would respawn (it takes about 20min to go through the list) [19:28] so using respawn, limit 2 600 [22:08] gchristensen: its perfectly kosher to have the shell code in the script/end script be "the program". Just not very easy to maintain. [22:09] gchristensen: were it my system, I'd put it somewhere else and exec that so that the upstart bit and the "code" are separate [22:16] soudns good. thank you SpamapS