| === juergbi_ is now known as juergbi | |
| [09:13] <keesj> Hi ppl | |
| [09:20] <keesj> I am STILL at 0.3.8 and hava a question about starting jobs | |
| [09:20] <keesj> when I run "start my_job_name" the system doesn't return ,(I need to use --no-wait as extra parameter) | |
| [09:20] <keesj> what does that mean? | |
| [09:29] <keesj> my test file looks like this http://paste-it.net/public/cd60791/ | |
| [10:15] <suihkulokki> keesj: start --no-wait | |
| [10:31] <keesj> suihkulokki: yes, but that doesn't work for me because my service is started when and other service is started | |
| [10:31] <keesj> so "start on starting myother_test" | |
| [13:10] <Keybuk> keesj: it won't return because you never stopped it | |
| [13:10] <Keybuk> you probably want "service" in there | |
| [15:21] <keesj> my file is called service_xxx :P | |
| [15:21] <keesj> what is service? | |
| [15:30] <keesj> Keybuk: It works!! | |
| [15:30] <keesj> great!! | |
| [15:31] <keesj> Keybuk saved the day | |
| [15:32] <Keybuk> jobs come in two types, "task" and "service" | |
| [15:32] <Keybuk> a task has to complete before it is "finished" | |
| [15:32] <Keybuk> a service merely has to be running | |
| [15:32] <Keybuk> therefore the start command waits for a task to start, run and then stop again | |
| [15:32] <Keybuk> whereas it only waits for a service to start and run | |
| [15:32] <Keybuk> in 0.3.x, the default for a job was a task | |
| [15:33] <Keybuk> so since you had no main exec/script, it ran until you issued a separate "stop" command | |
| [15:40] <keesj> it all gets messy when you start using emits in upstart scripts | |
| [15:40] <keesj> but so far it all works :P | |
| === notting__ is now known as notting | |
| [19:37] <sadmac2> Keybuk: good afternoon | |