Section: Environments, Tables, and Troff Macros (7)
Return to Main Contents
upstart-events - Well-known Upstart events summary
This manual page summarises well-known events generated by Upstart
running both as the
daemon (process ID 1) and a Session Init (process that supervises a user
It is not an exhaustive list of all possible events, but rather details
a standard set of events expected to be generated on any Ubuntu system
The primary tables, Table 1 and Table 2, encode the
well-known system and session events respectively, along with the type
of each event (listed in Table 3), the emitter of the event (see
Table 4) and the approximate time at which the event could be
generated. Additionally, the Note column indexes into Table
5 for further details on a particular event.
for a table summarising job goals and possible state transitions.
Note that some events listed in
be available to session jobs (depending on when the Session Init
starts). Those events that are available will be prefixed with
for further details.
The Ref (Reference) column is used to refer to individual
events succinctly in the Time column.
Note that the '<' and '>' characters in the Time column denote
that the event in the Event column occurs respectively before or
after the event specified in the Time column (for example, the
mounting(7) event occurs "at some time" after the startup(7)
event, and the virtual-filesystems(7) event occurs after the last
mounted(7) event relating to a virtual filesystem has been emitted).
For further details on events, consult the manual pages and the system
job configuration files, usually located in /etc/init.
Table 1: Well-Known System Events Summary.
|container||S||C||> /run mounted||Q|
|dbus-activation||S||B||> D-Bus client request|
|deconfiguring-networking||H||V||< non-local IFs down||P|
|desktop-session-start||H||D||> X(7) session created||B|
|desktop-shutdown||H||D||> X(7) session ended||O|
|failsafe-boot||S||X||> (7) and local IF||S|
|7||filesystem||S||M||After last (1)||D|
|login-session-start||H||D||< DM running||F|
|1||mounted(7)||H||M||> associated (2)||G|
|not-container||S||C||> /run mounted||Q|
|runlevel(7)||M||T||> (7) + (8)|
|socket(7)||S||S||> socket connection||X|
|started(7)||S||I||> job started||K|
|starting(7)||H||I||< job starts||K|
|static-network-up||S||N||> last static IF up|
|stopped(7)||S||I||> job stopped||K|
|stopping(7)||H||I||< job stops||K|
> last remote FS unmounted
|6||virtual-:filesystems(7)||S||M||> last virtual FS (1)||M|
'DM' is an abbreviation for Display Manager.
'FS' is an abbreviation for filesystem.
'IF' is an abbreviation for Network Interface.
Table 2: Well-Known User Events Summary.
Table 3: Event Types.
Blocking. Waits for events that start on or stop on this
Table 4: Event Emitters.
Table 5: Event Summary Notes.
Requires administrator to press Control-Alt-Delete key
combination on the console.
|B||Event generated when user performs graphical login.|
These are specific examples. upstart-udev-bridge(8) will emit
events which match the pattern, "S-device-A" where
'S' is the udev subsystem and 'A' is the udev action. See
udev(7) and for further details. If you have sysfs
mounted, you can look in /sys/class/ for possible values for subsystem.
|D||Note this is in the singular - there is no 'filesystems' event.|
Emitted when administrator presses Alt-UpArrow key combination on
Denotes Display Manager running (about to be displayed), but no users
logged in yet.
|G||Generated for each mount that completes successfully.|
Emitted when mount attempt for single entry from fstab(5)
for any filesystem type is about to begin.
|I||Emitted when Upstart receives the SIGPWR signal.|
|J||Initial event (system or Session Init).|
Although the events are emitted by init(8), the instigator may be
initctl(8) if a System Administrator has manually started or
stopped a job.
|M||Emitted when all virtual filesystems (such as /proc) mounted.|
Emitted when the --dev-wait-time timeout is exceeded for
mountall(8). This defaults to 30 seconds.
Emitted when the X(7) display manager exits at shutdown or reboot, to
hand off to the shutdown splash manager.
Emitted by /etc/init.d/networking just prior to stopping all non-local
Either 'container' or 'not-container' is emitted (depending
on the environment), but not both.
Emitted by either the initramfs or bootloader (for example grub) as the initial
event (rather than startup(7)) to denote the system has booted into
recovery mode. If recovery was successful, the standard startup(7)
event is then emitted, allowing the system to boot as normal.
Emitted to indicate the system has failed to boot within the expected
time. This event will trigger other jobs to forcibly attempt to bring
the system into a usable state.
|T||Only emitted for a graphical session.|
This is a pseudo-system event emitted directly by the
Emitted by Session Init only since bridge not run as system job by
Used primary by Session Job
Manual page written by James Hunt
Report bugs at
Copyright © 2011-2013 Canonical Ltd.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
- Event Summary
- REPORTING BUGS
- SEE ALSO
This document was created by
using the manual pages.
Time: 21:27:11 GMT, January 19, 2018