[15:42] <sadmac2> Keybuk: I have some progress on the state machine
[15:50] <ion_> Have you looked at ragel?
[15:50] <sadmac2> ion_: what is that?
[15:51] <ion_> apt-cache show ragel
[15:51] <sadmac2> ion_: redhat employee
[15:51] <suihkulokki> yum yum :P
[15:52] <ion_> I’m sure you’re able to apply the information. :-)
[15:52] <sadmac2> ion_: ah
[15:52] <sadmac2> ion_: not quite what what we need
[15:52] <ion_> Alright
[15:52] <sadmac2> it supports D?
[15:52] <sadmac2> o...k.....
[15:53] <sadmac2> good to see someone's interested
[15:57]  * Keybuk will be interested in November :p
[15:58] <sadmac2> Keybuk: I meant interested in D
[15:58] <sadmac2> Keybuk: and what's in November?
[16:02] <Keybuk> the start of the next release
[16:02] <Keybuk> and most importantly, the end of this one :p
[16:05] <sadmac2> ah
[16:05] <sadmac2> that'd do it
[22:38] <smagoun> I'm having trouble creating new upstart jobs - I have to reboot before initctl recognizes the job. My kernel has CONFIG_INOTIFY=y, so i expected the new job to be available immediately. I have upstart 0.3.9-2 on ubuntu 8.04. I checked permissions on the new job, they're fine (root/root, 0644). Any suggestions?
[22:39] <smagoun> specifically, 'start newjob' returns 'Unknown job' and 'initctl list' doesn't show the new job until I reboot