[16:48] So registering a new session job appears to require more than just the presence of a file in $HOME/.config/upstart/myupstartjob.conf [16:48] True? [16:49] I’m running upstart 1.12.1 on trusty 14.04 [16:49] mlindsay: no - that is sufficient. Is your job valid ('init-checkconf $HOME/.config/upstart/myupstartjob.conf')? [16:50] s3-router.conf: syntax ok [16:51] the reason I think it’s not running is ps aux | grep js returns nothing [16:51] and no corrosponding log file in /var/log/upstart [16:51] it’s all put together under a brand new user [16:52] so I created the .config/upstart dirs myself [16:52] mlindsay: /var/log/upstart is for *system* jobs, not session-level jobs. For those, look in $HOME/.cache/upstart/myupstarjob.log. [16:52] mlindsay: .config/upstart must exist before the session init starts (inotify limitation). [16:53] mlindsay: if that isn't the case, you should be able to run 'start re-exec' (non-root) to have the job picked up. [16:53] mlindsay: (and avoid having to log out). [16:53] jodh: do I have to create the .cache dir? [17:13] jodh: thanks for helping out, and sorry for any stupid questions, but when I ‘start re-exec’ I get start: Unknown job: re-exec [17:22] on a more general note, I’m setting this up as a session job for security reasons only, Is that appropriate? If not I’m working too hard [18:01] mlindsay: yes, you need to create the .cache dir if you want job output to be logged (it's not an error if it doesn't exist, but upstart will discard all job output). [18:01] mlindsay: are you running 'start re-exec' as a non-root user? [18:01] yes [18:03] nodejs-runner@ip-###-###-###-###:/home/ubuntu$ start re-exec [18:03] start: Unknown job: re-exec [18:08] funny thing is, with ~/.config/upstart/s3-router.conf present, service s3-router status says s3-router: unrecognized service === mlindsay_ is now known as mlindsay === jhford_ is now known as jhford