[15:39] <SpamapS> hrm.. console=tty0 console=ttyS0 .. wouldn't one expect that to try tty0, then ttyS0? I think upstart is doing that backwards
[21:25] <technomancy> if I want upstart not to stop a job but to prevent it from restarting once it does stop, what's the best way to do that? should I just remove the job config from /etc/init?
[21:27] <SpamapS> technomancy: you could just override all the important fields in /etc/init/jobname.override
[21:27] <SpamapS> technomancy: or maintain a sentinel file and check for it in pre-start
[21:28] <technomancy> I guess it's the "respawn" behaviour I want to disable
[21:28] <technomancy> so I could counteract that in a separate .override file?
[21:29] <SpamapS> technomancy: unfortunately no, thats a known bug. respawn can't be turned off in .override :-/
[21:30] <technomancy> ok. in this case if I comment out that line in the original conf file I should be OK since I only need it off for a short window now that I think of it.
[21:30] <SpamapS> technomancy: respawn only respawns on non-normal exits. If your program exits with a normal exit code or signal, respawn will not fire
[21:30] <SpamapS> technomancy: you can redefine the normal exits
[21:31] <SpamapS> technomancy: why is your program dying violently? Also if the goal is 'stop' then you won't have a respawn either
[21:31] <technomancy> SpamapS: good to know; thanks
[21:31] <technomancy> I'm sending haproxy a -SIGUSR1 which supposedly tells it to exit after all active connections have terminated and stop accepting new connections
[21:31] <technomancy> it doesn't appear to be behaving quite as documented, but that's a different issue
[21:32] <SpamapS> technomancy: normal exit SIGUSR1 should do it then
[21:32] <technomancy> should prevent a respawn you mean?
[21:32] <SpamapS> technomancy: upstart will respawn if the program dies from a signal that is not listed there
[21:32] <technomancy> I see; thanks