=== rm_work is now known as rm_work|away === rm_work|away is now known as rm_work === rm_work is now known as rm_work|away === rm_work|away is now known as rm_work === rm_work is now known as rm_work|away === rm_work|away is now known as rm_work === rm_work is now known as rm_work|away === rm_work|away is now known as rm_work [18:52] guys, anyone willing to check out my upstart script and see why it's respawning for ever? https://gist.github.com/Mariano-gon/8941403 [18:52] I think this is a env issue, as If I cd into newrelic plugin directory and run bundle exec .. it'll start without any issues; but it won't from anywhere else [18:53] I tried with env and export stanzas, nothing seems to work [18:57] Do you see its output in /var/log/upstart? [19:01] in /var/log/messages it's mine. https://gist.github.com/Mariano-gon/8941660 [19:02] and this same will repeat ten times and then stop [19:04] But do you see the *output* of the process in /var/log/upstart? [19:04] there's no upstart folder in /var/log.. [19:17] Ok. In that case you can add manual logging to the job. [19:17] script [19:18] exec >>/tmp/blah.out 2>&1 [19:18] set -x [19:18] exec sudo -u root … [19:18] end script [19:35] but doesn't the first exec (or the second) shut off the other one? [20:05] Debian went with systemd [20:05] they could have went with upstart [20:05] and probably would have if it weren't for upstart being under CLA [20:06] you guys lost Debian thanks to your CLA [20:06] now if there were anyone using upstart they will migrate to systemd [20:06] if there was anyone who considered upstart, they wont anymore, now everyone will be adopting systemd