[06:23] why is this config starting multiple processes of god initially, and then within a few seconds it's down to two of them that won't go away: http://pastie.org/1021409 [06:23] if I comment out the exec/respawn lines then god never gets started [06:24] all these commands are within a few seconds: http://pastie.org/1021413 [06:24] for some reason it killed all but one this time [14:06] Hi Keybuk [14:06] Working hard on 0.10? :-) [14:07] it consumes my every waking moment :p [15:05] anyone have any insight into this weirdness? https://answers.launchpad.net/upstart/+question/115996 [15:15] crankharder: I would guess that "god" forks multiple instances by itself [15:15] or is a daemonising process (so upstart sees the daemonisation as it existing badly) [15:20] well, 1) i dont think god forks itself 2) it doesn't do it if I execute the command manually 3) respawn on it is broken, if I kill all the processes it doesn't restart [15:20] "do it" == start multiple processes [15:21] also, weirdness like this: [15:21] $ sudo stop god [15:21] stop: Unknown instance: [15:35] that to me really implies that god forks [15:35] Keybuk: well yeah. Jesus. [15:50] are there repercussions if I add expect fork and expect daemon and god doesn't actually fork/daemonize something? [15:51] ...well, it works as expected w/ those added [17:36] Keybuk: is there any chance of an ubuntu developer working on randomly nonstarting services on 10.04? at work we are still installing 8.04 on customer systems due to this bug... [17:36] you'd have to ask your support contact about that [17:37] my employer is too cheap to pay canonical for support :) [17:37] I don't know of any bugs affecting large numbers of users in 8.04 [17:38] so if you do have an issue, it is probably specific to your configuration [17:38] the bug is in 10.04, LP#543506 and co. [17:38] sorry I mean 10.04 [17:39] isn't that the bug where /dev/console isn't available? [17:39] yes i think that's part of the problem [17:39] (well, the node exists, but opening fails) [17:48] right, the cause of that bug hasn't been found yet [17:49] and reading through the comments, multiple ubuntu developers are participating in the triage process [17:53] alright ... i don't really know which ones are ubuntu devs and which aren't of course :) well thanks for having a look [17:55] maybe i'll see whether i can reproduce it with a different kernel === Will| is now known as 77CAAT2SL === 77CAAT2SL is now known as Will| === Caesar_ is now known as Caesar === Psi-Jack_ is now known as Psi-Jack === soren_ is now known as soren