[Bug 701576] Re: Upstart should provide a generic network-services job for non-boot-critical network services to follow.

[Clint Byrum]

Excerpts from Steve Langasek's message of Tue Oct 04 00:02:17 UTC 2011:
> Clint, is this the 'static-network-up' job in oneiric, or is something
> else needed still?
> 

I would like to have an empty "meta" job that all other things follow,
so instead of

start on runlevel [2345]
stop on runlevel [!2345]

Which ties to sysvinit and doesn't obviously reflect the authors
intentions, we'd have

start on starting network-services 
stop on stopping network-services

This would probably just have the runlevel start on / stop on listed
above.

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

Title:
  Upstart should provide a generic network-services job for non-boot-
  critical network services to follow.

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: upstart

  This is a feature request for the Ubuntu upstart package.

  I posted the original description here:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2010-December/032254.html

  The summary is that rather than require all upstart jobs to know when
  exactly in the boot they want to start on and when exactly in the
  shutdown they want to stop on, we should provide a readable, common
  sense job whose started/stopping events can be followed, and whose
  starting/stopped events can be used to prime and cleanup the
  environment.

  A merge proposal will follow the filing of this bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/701576/+subscriptions