=== robbiew-afk is now known as robbiew === robbiew is now known as robbiew-afk === robbiew-afk is now known as robbiew [19:02] good evening [19:02] hi [19:03] i´ve a problem with upstart und shutdown the system [19:04] i emit the shutdown event [19:04] the job stats and some jobs stops [19:05] but then the the system halts and not all services are stopped clearly [19:06] is there way to check if all services are stopped bevore upstart power of the system ? [19:07] keesj: do you have any idea for this problem ? [19:07] Stevee: 1) are you sure there's reason to do that? For a lot of services its just a waste of time. 2) what do your job definitions look like now? [19:08] my job file looks like that [19:09] http://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=src/initscripts/core/shutdown.conf;h=394b2274636e58ed9bef1b58150b87a2b0ad3079;hb=1237e47913328b79e5908d0d2c77f855c054ac04 [19:09] if i remove the whole script [19:09] i got messages from als services that they have stopped on the console [19:09] if i start the job with the script section [19:10] i only get a message of 2 or 3 jobs [19:10] after that, the system powered off [19:10] and all other jobs aren´t killed clearly [19:10] Stevee: yes, that's going to halt the system as soon as it gets shutdown, with no regard to what else is going on [19:11] Stevee: do your other services have "stop on shutdown" and that is how they shut down? [19:11] yes, they have stop on shutdown or reboot [19:11] Stevee: yes. this won't work :) [19:12] mhm okay, why ? [19:12] Stevee: make them stop on some other event (stop-all say) and then add an emits stop-all stanza to your shutdown job, and in the script do initctl emit stop-all [19:14] and why i can´t use stop on shutdown or reboot ? [19:15] Stevee: everything that happens on shutdown or reboot will happen at the same time. [19:16] so if emits a stop-all, all services will be stopped [19:16] and than, the system will halt ? [19:16] or reboot ? [19:18] yes. [19:18] Stevee do you always have the same behaviour or not? [19:18] yes [19:18] allways the same [19:19] and do all your job directly depend or stop on "starting" shutdown? [19:19] (what version btw?) [19:19] no only on stop on shutdown or reboot [19:19] version is 0.6.3 [19:19] also the current one [19:20] on thing that can happen is that one script fails and this makes the rest fail [19:20] but without compatiblity ( no runlevels ) [19:21] Stevee: also I think you need stop on starting [19:22] the ohter problem I see is that your even is names after the job name [19:22] so shoulden't it be "stop on starting shutdow" so first everything is started before the schutdown script is executed [19:23] Stevee: he's right. Stop on starting shutdown will let you avoid having to do the emits/initctl emit [19:23] (I have not played much with 0.6.3 yet) [19:24] stop on starting shutdown or reboot, is that correct [19:24] or do i need [19:25] stop on starting shutdown [19:25] stop on starting reboot [19:25] i two lines ? [19:25] you are no longer allowed to have two lines any more [19:25] okay [19:25] stop on starting shutdown or starting reboot(I would guess) [19:27] okay, and do i have to change the job name to something other than shutdown like "anything" [19:27] ? [19:27] do you know a distribution that uses upstart fully event based ? [19:28] Stevee: you don't /have/ to rename the job, but its probably better practice to not have jobs and events with the same name [19:30] okay so if i name the event halt and the job shutdown, i add to all other jobfiles stop on starting halt or starting reboot [19:30] everything should work fine ? [19:30] you'll want stop on starting shutdown [19:30] starting [19:31] oh, the jobname, okay [19:31] the other jobs will then stop whenever something tries to start your shutdown job, and they will block that shutdown job until they have all stopped [19:35] oh, i see [19:35] i allways depended on the event [19:35] not on the started job [19:36] its still an event. started is the name of the event. shutdown is the first argument [19:36] yes, but i also have to change the eventname or ? [19:37] you can have an event named shutdown and a job named shutdown, and that's fine. but its confusing. [19:38] oh, okay [19:38] so i will try it now, i will give a feedback [19:38] thanks for your help [19:42] Stevee: one more tip [19:43] you can set the log-priority using initctl. and when set to verbose it can help to understand what is going on [19:45] now the shutdown / reboot worked fine [19:45] thanks [19:46] but how can i hide all the messages of the stopped services ? [19:53] Stevee: you'd have to do that on a service-by-service basis [19:53] yes, i used it as event by service [19:55] if you want, you can add us to your list of know distributions that are using upstart [19:56] we are a firewall distribution called ipfire [19:56] page: http://www.ipfire.org === robbiew is now known as robbiew_ [23:04] guy i´ve to go to bed, i wish you a nice evening and thanks for your help again [23:05] hopefully we will see you again [23:05] good bye