table of contents
upstart-events(7) | Miscellaneous Information Manual | upstart-events(7) |
NAME¶
upstart-events - Well-known Upstart events summaryEvent Summary¶
This manual page summarizes well-known events generated by the Upstart init(8) daemon. 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 running Upstart.Ref | Event | Type | Emit | Time | Note |
all-swaps | S | M | > (5) | ||
control-alt-delete(7) | S | A | > (5) | A | |
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 | |
device-not-ready | H | M | > (2) | N | |
drm-device-added | S | U | > (5) | C | |
failsafe-boot | S | X | > (7) and local IF | S | |
7 | filesystem | S | M | After last (1) | D |
graphics-device-added | S | U | > (5) | C | |
keyboard-request(7) | S | A | > (5) | E | |
local-filesystems(7) | S | M | > (6) | ||
login-session-start | H | D | < DM running | F | |
1 | mounted(7) | H | M | > associated (2) | G |
2 | mounting(7) | H | M | > (5) | H |
3 | net-device-added | S | U | > (5) | C |
net-device-changed | S | U | > (5) | C | |
net-device-down | S | F | < (4) | C | |
4 | net-device-removed | S | U | > (5) | C |
net-device-up | S | F,N | > (3) | C | |
not-container | S | C | > /run mounted | Q | |
power-status-changed(7) | S | I | > (5) | I | |
recovery | S | G | Boot (<5) | R | |
remote-filesystems(7) | S | M | > (6) | ||
runlevel(7) | M | T | > (7) + (8) | ||
socket(7) | S | S | > socket connection | ||
5 | startup(7) | S | I | Boot | J |
started(7) | S | I | > job started | K | |
starting(7) | H | I | < job starts | K | |
8 | static-network-up | S | N | > last static IF up | |
stopped(7) | S | I | > job stopped | K | |
stopping(7) | H | I | < job stops | K | |
unmounted-remote-filesystems | H | V | > last remote FS unmounted | L | |
6 | virtual-filesystems(7) | S | M | > last virtual FS (1) | M |
Key:
'DM' is an abbreviation for Display Manager.
'FS' is an abbreviation for filesystem.
'IF' is an abbreviation for Network Interface.
Table 2: Event Types.
Ref | Event Type | Notes |
H | Hook | Blocking. Waits for events that start on or stop on this event. |
M | Method | Blocking task. |
S | Signal | Non-blocking. |
Ref | Emitter | Notes |
A | System Administrator (initiator) | Technically emitted by init(8). |
B | dbus-daemon(1) | Run with "--activation=upstart" |
C | container-detect job | |
D | Display Manager | e.g. lightdm/gdm/kdm/xdm. |
F | ifup(8) or ifdown(8) | See /etc/network/. |
G | bootloader or initramfs | |
I | init(8) | |
M | mountall(8) | |
N | network-interface job | |
S | upstart-socket-bridge(8) | |
T | telinit(8), shutdown(8) | |
U | upstart-udev-bridge(8) | |
V | System V init system | |
X | failsafe job |
Table 4: Event Summary Notes.
Note | Detail |
A | Requires administrator to press Control-Alt-Delete key combination on the console. |
B | Event generated when user performs graphical login. |
C | 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. |
E | Emitted when administrator presses Alt-UpArrow key combination on the console. |
F | Denotes Display Manager running (about to be displayed), but no users logged in yet. |
G | Generated for each mount that completes successfully. |
H | 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. |
K | Although the events are emmitted by init(8), the instigator may be initctl(8) if a System Administrator has manually started or stopped a job. |
L | /etc/init/umountnfs.sh. |
M | Emitted when all virtual filesystems (such as /proc) mounted. |
N | Emitted when the --dev-wait-time timeout is exceeded for mountall(8). This defaults to 30 seconds. |
O | Emitted when the X(7) display manager exits at shutdown or reboot, to hand off to the shutdown splash manager. |
P | Emitted by /etc/init.d/networking just prior to stopping all non-local network interfaces. |
Q | Either 'container' or 'not-container' is emitted (depending on the environment), but not both. |
R | 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. |
S | 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. |
Job States¶
Table 5: Job Goals and State Transitions.
Goal | ||
_ | ||
Current State | start | stop |
waiting | starting | n/a |
starting | pre-start | stopping |
pre-start | spawned | stopping |
spawned | post-start | stopping |
post-start | running | stopping |
running | stopping | pre-stop / stopping (*) |
pre-stop | running | stopping |
stopping | killed | killed |
killed | post-stop | post-stop |
post-stop | starting | waiting |
Key:
(*) If there is a script or exec section and this process is running,
state will be 'pre-stop', else it will be 'stopping'.
Job Lifecycle¶
Starting a Job¶
- 1
- Initially the job is "at rest" with a goal of 'stop' and a state of 'waiting' (shown as 'stop/waiting' by the initctl(8) list and status commands).
- 0[step]
- The goal is changed from 'stop' to 'start' indicating the job is attempting to start.
- 0[step]
- The state is changed from 'waiting' to 'starting'.
- 0[step]
- The starting(7) event is emitted denoting the job is "about to start".
- 0[step]
- Any jobs whose 'start on' (or 'stop on') condition would be satisfied by this job starting are started (or stopped respectively).
- 0[step]
- The starting(7) event completes.
- 0[step]
- The state is changed from 'starting' to 'pre-start'.
- 0[step]
- If the pre-start stanza exists, the pre-start process is spawned.
- 0[step]
- If the pre-start process fails, the goal is changed from 'start' to 'stop', and the stopping(7) and stopped(7) events are emitted with appropriate variables set denoting the error.
- 0[step]
- Assuming the pre-start did not fail or did not call "stop", the main process is spawned.
- 0[step]
- The state is changed from 'pre-start' to 'spawned'.
- 0[step]
- Upstart then ascertains the final PID for the job which may be a descendent of the immediate child process if expect fork or expect daemon has been specified.
- 0[step]
- The state is changed from 'spawned' to 'post-start'.
- 0[step]
- If the post-start stanza exists, the post-start process is spawned.
- 0[step]
- The state is changed from 'post-start' to 'running'.
- 0[step]
- The started(7) event is emitted.
- 0[step]
- Any jobs whose 'start on' (or 'stop on') condition would be
satisfied by this job being started are started (or stopped respectively).
Stopping a Job¶
- 1
- Assuming the job is fully running, it will have a goal of 'start' and a state of 'running' (shown as 'start/running' by the initctl(8) list and status commands).
- 0[step]
- The goal is changed from 'start' to 'stop' indicating the job is attempting to stop.
- 0[step]
- The state is changed from 'running' to 'pre-stop'.
- 0[step]
- If the pre-stop stanza exists, the pre-stop process is spawned.
- 0[step]
- The state is changed from 'pre-stop' to 'stopping'.
- 0[step]
- The stopping(7) event is emitted.
- 0[step]
- Any jobs whose 'start on' (or 'stop on') condition would be satisfied by this job stopping are started (or stopped respectively).
- 0[step]
- The main process is stopped:
- 1
- The signal specified by the kill signal stanza is
sent to the process group of the main process (such that all processes
belonging to the jobs main process are killed). By default this signal is
SIGTERM.
- 0[step2]
- Upstart waits for up to "kill timeout" seconds (default 5 seconds) for the process to end.
- 0[step2]
- If the process is still running after the timeout, a SIGKILL signal is sent to the process which cannot be ignored and will forcibly stop the processes in the process group.
- 0[step]
- The state is changed from 'killed' to 'post-stop'.
- 0[step]
- If the post-stop stanza exists, the post-stop process is spawned.
- 0[step]
- The state is changed from 'post-stop' to 'waiting'.
- 0[step]
- The stopped(7) event is emitted.
- 0[step]
- Any jobs whose 'start on' (or 'stop on') condition would be
satisfied by this job being stopped are started (or stopped respectively).
AUTHOR¶
Manual page written by James Hunt <james.hunt@ubuntu.com>REPORTING BUGS¶
Report bugs at <https://launchpad.net/ubuntu/+source/upstart/+bugs>COPYRIGHT¶
Copyright © 2011-2012 Canonical Ltd.SEE ALSO¶
init(5) init(8) initctl(8) mountall(8) started(7) starting(7) stopped(7) stopping(7) telinit(8)2011-03-24 | upstart |