[12:57] <marianogg9> hi guys
[12:57] <marianogg9> is there a stanza to set the ulimit?
[13:34] <jodh> marianogg9: Yes, the 'limit' stanza - see http://upstart.ubuntu.com/cookbook/#limit and init(5).
[13:47] <marianogg9> thanks jodh
[15:07] <sleepycat> I have an upstart service stuck in stop/killed state, and it looks like some combination of forks has screwed things up. The ps command shows nothing is running but upstart won't let me start this thing again. How can I convince Upstart that this job is dead (without restarting the server)?
[15:10] <jodh> sleepycat: see http://upstart.ubuntu.com/cookbook/#expect, http://upstart.ubuntu.com/cookbook/#implications-of-misspecifying-expect, http://upstart.ubuntu.com/cookbook/#recovery-on-misspecification-of-expect. If you are unlucky, I'm afraid you cannot force upstart to forget about that job until a reboot occurs.
[15:11] <jodh> sleepycat: however, if you simply need to fix the job and restart that service, you may be able to fix the syntax in the original .conf, then copy it to new.conf, remove the 'start on' (to avoid it starting on next boot) and manually "sudo start new".
[15:12] <jodh> sleepycat: note that with the advent of user sessions you can test a job using a session init (as root) "sudo init --user --confdir /tmp/init/" and if the job fails for whatever reason, just kill that secondary upstart instance. Repeat and once fully tested, deploy to /etc/init/.
[15:13] <jodh> sleepycat: or use a VM / container of course.
[15:22] <sleepycat> jodh: Hmm. OK, I think the new job thing is a good idea.
[15:31] <sleepycat> jodh: Thanks!