[18:58] does "start on stopped job ok" still work? [18:58] I ask because it doesn't seem to here [18:58] Zeqadious: version? [18:58] 0.5.1 [18:59] Zeqadious: start on stopped job RESULT=ok [18:59] sweet [18:59] whats the other RESULT? [18:59] RESULT=failed? [18:59] surprisingly [18:59] Zeqadious: although I'd think that would still work... maybe its changed a bit. There's a way [19:00] other result was failed I think [19:00] ok [19:00] you can also just shortcut RESULT=failed and just check EXIT_STATUS=* or something [19:00] I removed all the ok's [19:00] i'll put them back now [19:00] start on stopped job EXIT_SIGNAL=11 etc. [19:00] * sadmac2 tries to imagine the task you want to run on segfault and nowhere else [19:01] start on stopped EXIT_SIGNAL=11 [19:01] exec apport-auto-file $JOB [19:02] Keybuk: wouldn't you want SIGABRT in there too? [19:03] also SIGILL, SIGFPE, possibly SIGPIPE [19:35] hmmm "start on started udev-daemon RESULT=ok" should work right? [19:36] it should [19:36] unless it became OK or something like that. [19:36] * sadmac2 doesn't have the code in front of him to check on these things [19:36] i'll try that.. [19:37] fsck comes after that, but its not starting for some reason [19:37] Zeqadious: you could do a start on started udev-daemon and then in the job definition do an export > /tmp/somefile and then look at somefile and see what its getting set to [19:38] export what though? [19:39] export RESULT > /tmp/$job.result ? [19:39] oops [19:39] $RESULT [19:40] Zeqadious: I meant set [19:41] Zeqadious: no arguments [19:41] * sadmac2 begins to realize how many ways unix has to list all the environment variables [19:41] env [19:41] set does it too [19:41] really? [19:41] export I think does a superset of it [19:42] yes [19:42] never tried that [19:42] so it does [19:43] i'll check the result now [19:44] lol, forgot that before fsck the fs is ro [19:45] hmm. just echo it then. stdout should display it [19:45] yep [19:47] well it has no result really [19:47] the environment should be small [19:47] at least there is no variable called RESULT [19:47] it is [19:47] UPSTART_EVENTS=started [19:47] closest thing i can find [19:47] odd [20:06] is this the correct way to use the expressions with the start on stanza http://zeqadious.homelinux.net/junkbin/upstart-0.5.1-jobs/sysinit/save-dmesg ? [20:09] Zeqadious: maybe... what do you think that will do?' [20:09] I think it should start when all conditions inside ( ) are met [20:10] but i may not need the ( ) [20:10] Zeqadious: they aren't conditions. They're events. It will start when all the things inside () /happen/ [20:10] and you need either the \s or the ()s, not both [20:10] oh? [20:10] oh. [20:11] it won't tell me that there are unknown stanzas when it sees and started sysinit/cleanup RESULT=ok on a line all by itself? [20:12] Zeqadious: it assumes the line continues until the closing parenthesis [20:12] thats great [20:12] looks a lot nicer [20:38] well that doesn't seem to work right. that job never starts and afaik those other jobs are all RESULT=ok [20:42] Zeqadious: are all of them started in the first place? [20:42] yes [20:42] ok. that's the usual reason these things break... [20:45] hardest part i'm finding with these upstart scripts is trying to make them robust enough to deal possible breaks [20:45] example? [20:47] i'm having issues with fsck script for example. its silently hangs quite often and I can't seem to track why or when. or like when some script may fail but won't report a failure and so my save-dmesg script never runs but i can't see why :) [20:48] first one sounds like an fsck issue [20:49] probably [21:01] aha [21:48] status job should return something right? [21:51] I think so [21:51] yes. the manpage confirms [21:51] initctl status job [21:51] (there's no symlink for status, I don't think) [21:52] initctl status job returns nothing too [21:52] it should shouldn't it? [21:52] on 0.5 it might only if the job is running [21:53] returns nothing if the job is running [21:53] returns nothing if the job isn't running too [21:53] weeeeird [21:54] what does it return with no argument? [21:54] I think the problem this indicates is what is making it so difficult for me to write the scripts. RESULT=ok for any respawning service doesn't work [21:54] initctl status returns all jobs with either running or not running [21:54] ok, so that works [21:55] ah, so the respawn flag kills the RESULT variable [21:55] bug. [21:55] aha [21:55] also my scripts are all in directories inside jobs.d like jobs.d/service/hald so the job is service/hald [21:56] but because of the mangle bug status service/hald returns nothing [21:56] just found that status service_2fhald works though [21:56] yeah. that's not a new one. [21:56] yeah i saw that one in the bug list [21:57] this is just the first instance where i had to type the mangled form in to get it to work [22:02] respawn is broken in many ways in 0.5 [22:08] well i filed a bug [22:09] 5pm works out. thanks for the help all, i'm going home.