[Bug 793554] [NEW] Add emits stanza for deconfiguring-networking

[James Hunt]

Public bug reported:

Binary package hint: dbus

The initctl(8) check-config command reads the "emits" stanzas (see
init(5)). However, we have a minor problem in that dbus starts on an
event that is not advertised using "emits":

$ initctl check-config
dbus
  stop on: unknown event deconfiguring-networking
$

This event is actually emitted by the SysV script /etc/init.d/networking
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
deconfiguring-networking event:

  emits runlevel
+ deconfiguring-networking

This will pacify "initctl check-config" without having to resort to the
--ignore-events option.


See also bug 791866.

** Affects: dbus (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: bitesize

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/793554

Title:
  Add emits stanza for deconfiguring-networking

Status in “dbus” package in Ubuntu:
  New

Bug description:
  Binary package hint: dbus

  The initctl(8) check-config command reads the "emits" stanzas (see
  init(5)). However, we have a minor problem in that dbus starts on an
  event that is not advertised using "emits":

  $ initctl check-config
  dbus
    stop on: unknown event deconfiguring-networking
  $

  This event is actually emitted by the SysV script
  /etc/init.d/networking 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
  deconfiguring-networking event:

    emits runlevel
  + deconfiguring-networking

  This will pacify "initctl check-config" without having to resort to
  the --ignore-events option.

  
  See also bug 791866.