| 2011-06-06 14:00:58 |
James Hunt |
description |
Binary package hint: upstart
The initctl(8) check-config command reads the "emits" stanzas (see init(5)). However, we have a minor problem in that portmap starts on an event that is not advertised using "emits":
$ initctl check-config
portmap
stop on: unknown event unmounted-remote-filesystems
$
This event is actually emitted by the SysV script /etc/init.d/umountnfs.sh which poses a problem in that we cannot update the appropriate Upstart .conf file, since there isn't one.
I propose the best solution is to add an appropriate emits line to /etc/init/rc-sysinit.conf in the Ubuntu Upstart package for the unmounted-remote-filesystems package:
emits runlevel
+ emits unmounted-remote-filesystems
This will pacify "initctl check-config" without having to resort to the --ignore-events option. |
Binary package hint: upstart
The initctl(8) check-config command reads the "emits" stanzas (see init(5)). However, we have a minor problem in that portmap starts on an event that is not advertised using "emits":
$ initctl check-config
portmap
stop on: unknown event unmounted-remote-filesystems
$
This event is actually emitted by the SysV script /etc/init.d/umountnfs.sh which poses a problem in that we cannot update the appropriate Upstart .conf file, since there isn't one.
I propose the best solution is to add an appropriate emits line to /etc/init/rc-sysinit.conf in the Ubuntu Upstart package for the unmounted-remote-filesystems event:
emits runlevel
+ emits unmounted-remote-filesystems
This will pacify "initctl check-config" without having to resort to the --ignore-events option. |
|
