[04:33] <nagchampa> hi guys, i've got a problem where my fakeraid (required for dual booting) is partitioned using gpt and dmraid won't initialise the partitions when it starts the raid, falling back instead on the gpt protection mbr record
[04:34] <nagchampa> i can use kpartx to initialise the partitions but i'd like to have a boot script do it automatically
[04:34] <nagchampa> is there an event i should be trying to hook in order to run before local filesystems are mounted
[04:35] <nagchampa> or should i be doing it another way
[04:35] <nagchampa> i'm looking through existing jobs and having trouble finding which events i should be waiting on
[04:46] <nagchampa> is there a way to ensure my script runs before certain local filesystems are mounted?
[04:46] <nagchampa> or will I have to modify the mountall job as well?
[04:49] <nagchampa> would "start on (mounting)" be the correct way to do it? would that cause my script to run before local filesystems are mounted?
[04:53] <nagchampa> or would it be better to use "start on (starting mountall)"
[05:08] <nagchampa> or considering the mountpoints for these filesystems won't be available until my script runs, would it be sufficient to just have it run on startup?
[06:48] <pmjdebruijn> hi all
[06:49] <pmjdebruijn> start on started networking should make sure a script would only run after networking is up right?
[06:49] <pmjdebruijn> for something that is dependant on domain name resolution
[08:27] <pmjdebruijn> hmmm I just I should use net-device-up
[08:27] <pmjdebruijn> sorry /just/guess/
[08:41] <ustunozgur> Hi, I'm trying to use upstart for a daemon written with python-daemon. However I couldn't find any correct documentation, http://upstart.at/2011/02/01/process-less-jobs/ for example doesn't seem to help. The daemon can currently be started as mydaemon start, stopped with mydaemon stop etc. 
[08:42] <ustunozgur> Should I go with the system-v style recommended there?
[08:43] <ustunozgur> Also, sometimes after I make changes, the tab completion after issuing start doesn't work, why? Is it because of errors in conf.
[09:05] <twb> What's the default signal sent to food on "stop foo"?
[09:05] <twb> TERM looks like
[09:06] <twb> Which is what poff sends by default to pppd, so now I'm having upstart control pppd directly, that should still be fine and pppd is still likely to run the iproute2 commands I put in /etc/ppp/ip-down.d/