doc: document/register the "start on" events

Bug #663983 reported by At Santos on 2010-10-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
James Hunt

Bug Description

it is not clear what are the "start on" events.

I had to search to find:
start on local-filesystems
found on:

I believe something as fundamental as "start on local-filesystems" should be documented somewhere in the core documentation.
(and "man upstart" tells you almost nothing)

I think to help with this, when someone writes a new package which provides new events for upstart, they should submit the new event to the upstart development group. The new event would then get added to a registry of upstart events.
This is kind of how IANA does it - and then the list of allowed values for any parameter is published.
For example,

Scott James Remnant (scott) wrote :

(Sorry, hit the wrong status).

Btw, did you try "man local-filesystems" ? There is actually a man page for most core events, but no single man page linking them together yet - though James has been working on just that.

I don't agree with the IANA approach though

Changed in upstart:
status: New → Invalid
status: Invalid → Triaged
importance: Undecided → Wishlist
assignee: nobody → James Hunt (jamesodhunt)
Changed in upstart:
status: Triaged → In Progress
James Hunt (jamesodhunt) wrote :

Upstart on Ubuntu (Natty) now includes a "well-known events" manual page:

  man 7 upstart-events

Note that it is not in the Upstream version of Upstart since it contains Ubuntu-specifics. If you are not running Natty, you can find the man page here:

Having downloaded it, view it like this:

    tbl upstart-events.7 | nroff -man | less

Alternatively, I've created a PDF version (doesn't render very nicely, but the content is there):

Changed in upstart:
status: In Progress → Fix Released
Scott James Remnant (scott) wrote :

James, STOP changing the status of upstream bug tasks to represent the status in Ubuntu.

Changed in upstart:
status: Fix Released → In Progress
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers