[11:16] Hi [11:23] I am hitting a old bug that the env are not taken into account on restart [11:23] I am searching for a bug report for that but can't seem to find it (/me need ammo to upgrade to 0.5) [11:37] where is Keybuk? [13:41] BTW, a debian user too reported that $REMOVE_CMD is broken [18:55] is it possible to act on custom events sent by initctl emit in upstart 0.3.9 (the one included in hoary) [18:58] Millox: yes [18:58] Millox: no settup. Just initctl emit anystringyoucanthinkof [18:59] and start on thatstring [19:02] well, i'm trying just that but somehow it doesnt work [19:03] in the configfile I have "start on blah" but "initctl emit blah" doesn't start the service [19:03] actually it sometimes say Unknown stanza [19:04] Millox: pastebin your entire job definition [19:05] hmm, should I use several stop on .. or should I use stop on blah or bleh? [19:05] depends [19:06] in 0.3.9 several stop on will work [19:06] in 0.5 it won't [19:06] okay [19:07] this is the start on and stop on definitions: [19:07] start on (quagga and firewall) or router-up [19:07] stop on router-down [19:07] stop on runlevel 0 [19:07] stop on runlevel 1 [19:08] stop on runlevel 6 [19:08] there is also a post-start script which enables routing and a post-stop which disables routing [19:09] start router and stop router works fine [19:09] sorry about the spamming [19:09] log says: [19:09] init: /etc/event.d/router: unable to read: Invalid argument [19:10] dunno that 0.3.9 has an and operator [19:10] or parens [19:11] not too sure though :O [19:11] maybe it doesn't [19:11] I just removed them and now the invalid argument isn't seen anymore [19:12] however, it still doesn't work [19:12] hm [19:23] okay, now i managed to get the bounce example working but I still havn't the foggiest why the other doesn't work [19:23] hmm [19:30] just tried adding a script stanza containg just /bin/true (and exec as well) but it still doen't work [19:34] try doing it without any and or or operators or parens at all [19:37] tried with only one start on and one stop on but nothing [19:39] hmm [19:39] hsuccess! [19:39] unfortunately i managed to shut down my router in the process ;-) [19:45] apparently you can't have dash in signal names [19:47] changing only the signal names is the difference between invalid argument and succes [19:47] s [19:48] unfortunately the start process doesn't return [19:48] now [19:51] hm [19:51] ah, service solved that [19:52] okay, now I'm confused [19:53] I've changed everything so much now that I dont know what I changed anymore [19:53] but now it works as it should [19:55] heh [20:03] okay, another question: the way to emit a signal from a job description is executing /sbin/initctl emit, right or wrong? [20:04] right [20:08] isn't the job supposed to not run if any of the pre,post-start,stop scripts return nonzero? [20:11] pre-start maybe [20:12] the rest of those I think it keeps going [20:20] seems like it yes [20:20] post-start things are already running, so its too late [20:20] post stop things are already stopped, so...now what? [20:21] pre-stop, well you don't want to make it impossible to stop something ever really [20:26] no, that seems reasonable [20:26] I just hadn't thought about it really [20:27] and I suppose, it would be better to spell correctly so that the script doesn't return nonzero :-/ [20:36] hmm, I don't feel that the service jobs works correctly... [20:36] i had a problem just now with jobs not starting [20:37] i have a "bogus" job called network which is basically a placeholder for all network starting, and i had only an emitted signal in this job [20:38] firewall and quagga had start on starting network in their job description [20:40] when I had script or exec /sbin/initctl the network first started and then stopped immideately whereas if I used pre-start and no exec or script stanza the network started [20:40] may [20:40] maybe I've completely misunderstood the stanzas [21:41] how is the environment set up for scripts, for instance is pid available through a variable in post-start/pre-stop? === AlexExtreme is now known as root === root is now known as AlexExtreme