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