[12:33] sadmac: pong [14:06] so, i tried implementing managing of my fastcgi processes via upstart.. seemed to work fine, then the server died and couldn't start. running ubuntu 8.04, and my best guess is that the starting is done at the same time as rc2 and by then fastcgi can't start (or something like that, I don't know much about init/upstart).. any general ideas how to make sure such things work as they should? [14:14] maybe i can add "initctl emit lighttpd_loaded" in lighttpd init.d script and use that as starting signal for fastcgi? is that a bad idea in any way? [15:57] o_cee: sounds ok to me [15:58] ion_: would you care to write test cases? [15:58] I need someone to test the state machine prototype [15:58] someone that didn't write it :)\ [16:19] sadmac: I don’t feel good enough to write any code at the moment, but perhaps some other day. [16:20] ion_: k [16:32] sadmac: mkay, i'll give it a try.. or i could have it depend on rc2 so that it's fully started before doing fastcgi? then i'd be sure everything else is running [16:33] o_cee: either works. may as well do the first one though. more upstarty [16:33] allrighty, thanks [16:33] o_cee: in fedora, we have initctl calls in /etc/rc that emit starting and started events for all the sysv scripts [16:34] sadmac: ah okay, sounds good. btw, any idea when for example ubuntu will be all upstart? [16:35] o_cee: when we're done rewriting it :) [16:35] ah :) [17:21] to avoid editing the init scripts in init.d (where my edits eventually be overwritten), can i do "start on started rc2"? would that work? [17:21] yes [17:22] that will start it after all of rc2 is done, right? [17:22] yes [17:22] cool, thanks. and what i have now, "start on runlevel 2" would make it start at the same time, thus probably creating my problem [17:23] yep [17:23] cool :) the box is a server half of sweden away from me so i don't like when it doesn't restart hehe ;)