[01:55] <Unit193> Sooo, is there a way to unwedge upstart then?  As in, when it loses track of a job and still thinks it's running, but you can't start or stop it?  (Causing upgrades to not work)
[10:37] <adrien_oww> xnox: well, for my issue, I've reverted some changes back without effect; I don't understand what is wrong but it's most probably a recent change on my end
[10:37] <adrien_oww> I have to change topic a bit but I'll get back to this when I can
[15:55] <magmatt> I've got an upstart script that when stopped doesn't stop all the child processes: http://paste.ubuntu.com/6484975/  This shows the problem: http://bpaste.net/show/yS98t42s9ki5umrFFDoG/  Why isn't that last processes killed when its parent is killed?
[15:55] <magmatt> you can see it lingering in line 16 of the second paste
[15:56] <magmatt> afaik there's no forking going on; nothing daemonizes
[16:07] <xnox> magmatt: this is very odd job.
[16:07] <magmatt> it looks like the su might be doing some kind of daemonizing
[16:07] <magmatt> xnox: yeah, it kind of is :(
[16:08] <xnox> magmatt: setuid shampain; setgid shampain; exec /home/shampain/start-shampain.sh
[16:09] <xnox> magmatt: instead of using su, cause stopping will be killing su.....
[16:09] <xnox> magmatt: with setuid/setgid stanzas you will not need su.
[16:09] <xnox> magmatt: you might be required to export/set $HOME
[16:09] <magmatt> xnox: okay, let me try that
[16:10] <xnox> magmatt: ideally you would not have wrapper script, but write it out directly in script stanza.... but not sure how to deal with decrypt thing.
[16:11] <magmatt> which brings me to another question: sometimes when I can the upstart conf script, I can't start/stop/restart because it complains of "stop: Unknown job: shampain"
[16:11] <magmatt> such is the case right now
[16:11] <magmatt> s/can/change/
[16:13] <xnox> you must have made a mistake, and it rejected the conf file.
[16:13] <xnox> init-checkconf /path/to/your/job.conf
[16:13] <xnox> should say what it complains about.
[16:15] <magmatt> xnox: I don't have init-checkconf, but the setuid and setgid stanzas are the problem (commenting them out make it work again).  I'm using upstart 0.6.5
[16:15] <magmatt> perhaps that's why
[16:15] <xnox> ah.
[16:15] <xnox> that's rather old.
[16:16] <xnox> magmatt: in that case, instead of using su -c, use start-stop-daemon and pass command/user args to it. then stop will send singnals to start-stop-daemon, which will in turn relay them.
[16:16] <xnox> it accepts --user option, etc.
[16:17] <magmatt> xnox: great!  Let me give that a try.  (And I'll see if ops is willing to upgrade upstart)
[16:23] <magmatt> bah, this box doesn't have start-stop-daemon either :(
[16:24] <magmatt> xnox: thank you for your help.  You've given me plenty to go on -- I'll need to see what we can do about installing things on this machine