| xx4h | "emits SOMETHING" in upstart can also be used for "stop on stopping SOMETHING" afterwards? | 09:23 |
|---|---|---|
| xx4h | meeh. where is the "umount" being handled for shutdown? | 09:54 |
| jodh | xx4h: /etc/init.d/umount* | 10:02 |
| xx4h | so upstart runs and there will run some init.d/* ? | 10:03 |
| xx4h | afterwards? at which point umount is called... | 10:04 |
| xx4h | how to trigger something to stop in upstart latest time possibe before umount is running? | 10:05 |
| jodh | xx4h: Upstart initiates the shutdown but unmounting of disks is currently handled by the sysv scripts for compatibility. Hence, if you want to modify the shutdown, you will need to modify those scripts. | 10:15 |
| xx4h | ok...first of all, thanks for your time-investigations...further -> what happens to upstart processes which doesn't contain a "stop on ..."-line? maybe you have a/some link(s) to a documentation on this? | 10:17 |
| jodh | xx4h: http://upstart.ubuntu.com/cookbook/#job-with-start-on-but-no-stop-on. It is really a bug if jobs do not specify a 'stop on'. Also, sendsigs needs to be more aggressive to deal with such buggy jobs. | 10:53 |
| xx4h | ok, thank you...in summary...it will be a big thing to stop rsyslogd just before umounts are starting... | 10:55 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!