| mkomitee | I understand that 'start on runlevel' will start as soon as we switch to that runlevel. Is there a way to cause a job to start only once all of the services associated with that runlevel have completed? | 19:19 |
|---|---|---|
| SpamapS | mkomitee: unfortunately no, but I have an idea for how to make that happen. | 19:22 |
| mkomitee | FYI I'm on rhel6 so I'm running upstart, but there's a lot going on with the legacy sysv init system. | 19:23 |
| SpamapS | mkomitee: we need to have things 'start on starting network-services'. network-services would be 'start on runlevel [2345]' .. then you could do 'start on started network-services' to be "after normal stuff" | 19:23 |
| SpamapS | mkomitee: for rhel6 you might be able to fake it with 'start on stopped rc RUNLEVEL=x | 19:23 |
| mkomitee | any idea what emits that? | 19:24 |
| mkomitee | or do all tasks emit something when they complete? | 19:25 |
| mkomitee | aha, that appears to be the case, so when rc is finished, it'll emit "stopped rc" | 19:26 |
| mkomitee | so I can create a task which will "start on stopped rc RUNLEVEL=[2345]" and it should start whenever all of the services that require it have been stopped/started in the sysv system. | 19:27 |
| SpamapS | mkomitee: right, that would work in Ubuntu too | 19:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!