[01:07] so, I'm running a python daemon that starts up with double forking and for some reason "expect daemon" doesn't cause it to track the correct pid and it is tracking the initial pid before any forks take placeā€¦are there known issues with expect daemon? [01:16] herriojr: how are you launching it? [01:16] herriojr: is the python daemon launched with exec stanza? [01:35] @xnox: not the whole file, but the section you asked for: http://pastebin.com/N70HXzZB [01:40] herriojr: you want "... all the environment ... exec python " or "exec ... all the environment ... python " [01:40] try both of those and see if one or both of them work and do what you need. [01:41] xnox: are you saying use exec instead? [01:41] and can I do that in the script section or do I do it as a separate section? [01:41] herriojr: just as it is inside script section. [01:43] herriojr: see line 46 for example https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/raring/xinetd/raring/view/head:/debian/xinetd.upstart#L46 [01:43] couldn't find one with envrionment variables as well. [01:44] is that just so it can identify the command that is being daemonized? [01:44] exec is kind of an indicator as to "start counting forks from here" marker. [01:44] ah ok [01:44] yes. [03:45] alright, I figured out my issue: https://bugs.launchpad.net/upstart/+bug/799884 [04:10] so can "expect stop" be used in place of "expect daemon" to report the pid of the daemon process? [06:53] I'm writing a near-trivial job for an Ubuntu 10.04 system, which is upstart 0.6.5-8. Are you guys interested in discussing that, or is that old enough to be "upgrade or GTFO" territory? [06:58] http://paste.debian.net/243300/ well anyway, that's what I've got. [06:59] It all works... except "start streamrippers" never exits. It's starting the individual streamripper jobs OK tho. [07:00] http://paste.debian.net/243301/ [20:51] why can't I run init-checkconf as root?