[19:07] <jouk> noob here, I have an error in my /etc/init/foo.conf. I fixed the file, but when I try to "stop", the fix is not present. It looks like it's using a cached file somewhere
[19:07] <jouk> How do I make upstart "reload" my new foo.conf?
[19:11] <astrumas> jouk: Is this what you mean? http://upstart.ubuntu.com/faq.html#reload
[19:12] <astrumas> Supposedly it should do it automatically, but looks like you can force it.
[19:13] <jouk> hm, the problem is that the "stop" command does not work (that's what I fixed)
[19:13] <jouk> so when I try to initctl reload, the same error occurs
[19:14] <astrumas> Hmm... is it safe for you to kill the job the hard way?
[19:14] <astrumas> Or even reboot the machine if thats possible in your environment, heh
[19:15] <jouk> astrumas: what's the hard way?
[19:17] <astrumas> initctl list, find your running jobs, "process XXX", where XXX should be the PID, then "kill XXX".
[19:17] <astrumas> Essentially kill all the jobs that use that config and try to restart them.
[19:17] <jouk> oh, yeah I can do that. let me give it a shot