upstart-events man page on ElementaryOS

Man page or keyword search:  
man Server   4994 pages
apropos Keyword Search (all sections)
Output format
ElementaryOS logo
[printable version]

upstart-events(7)					     upstart-events(7)

NAME
       upstart-events - Well-known Upstart events summary

Event Summary
       This manual page summarises well-known events generated by Upstart run‐
       ning both as the init(8) daemon (process	 ID  1)	 and  a	 Session  Init
       (process that supervises a user session).

       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.

       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 particu‐
       lar event.

       See init(8) for a table summarising job goals and possible state	 tran‐
       sitions.

       Note  that  some	 events	 listed in Table 1 may be available to session
       jobs (depending on when the Session Init starts). Those events that are
       available  will be prefixed with :sys:. See upstart-event-bridge(8) for
       further details.

       The Ref (Reference) column is used to refer to individual  events  suc‐
       cinctly 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-filesys‐
       tems(7) event occurs after the last mounted(7) event relating to a vir‐
       tual 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.

┌────┬──────────────────────────┬──────┬──────┬────────────────────────┬──────┐
│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   │
│    │ file			│  S   │  K   │ > (1)		       │  U   │
│ 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)		       │      │
│    │ rotate-logs		│  H   │  R   │ hourly		       │  Y   │
│    │ runlevel(7)		│  M   │  T   │ > (7) + (8)	       │      │
│    │ socket(7)		│  S   │  S   │ > socket connection    │  X   │
│ 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-	│  H   │  V   │ >   last   remote   FS │  L   │
│    │ filesystems		│      │      │ unmounted	       │      │
│ 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: Well-Known User Events Summary.

┌────┬──────────────────┬──────┬──────┬─────────────────────────────────┬──────┐
│Ref │	    Event	│ Type │ Emit │		     Time		│ Note │
├────┼──────────────────┼──────┼──────┼─────────────────────────────────┼──────┤
│    │ dbus		│  S   │  L   │ > (1)				│  W   │
│    │ dconf		│  S   │  O   │ > (1)				│      │
│    │ desktop-end(7)	│  S   │  J   │ < (2)				│      │
│    │ desktop-start(7) │  H   │  J   │ > (3)				│      │
│    │ file		│  S   │  K   │ > (1)				│  U   │
│ 2  │ session-end(7)	│  M   │  I   │ < Session Init end		│      │
│ 1  │ startup(7)	│  S   │  I   │ > Session Init start		│  J   │
│    │ :sys:*		│  S   │  E   │ > upstart-event-bridge(8) start │      │
│    │ :sys:restarted	│  S   │  E   │ > upstart-event-bridge(8) start │  V   │
│ 3  │ xsession		│  M   │  H   │ > (1)				│  T   │
└────┴──────────────────┴──────┴──────┴─────────────────────────────────┴──────┘

Table 3: 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.	│
└────┴────────────┴─────────────────────┘

Table 4: Event Emitters.

┌────┬──────────────────────────────────┬─────────────────────────────────┐
│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.	  │
│ E  │ upstart-event-bridge(8)		│				  │
│ F  │ ifup(8) or ifdown(8)		│ See /etc/network/.		  │
│ G  │ bootloader or initramfs		│				  │
│ H  │ xsession-init session job	│				  │
│ I  │ init(8)				│ Either PID 1 or a Session Init. │
│ J  │ job that starts desktop		│ gnome-session job for Ubuntu.	  │
│ K  │ upstart-file-bridge(8)		│ See file-event(7).		  │
│ L  │ upstart-dbus-bridge(8)		│ See dbus-event(7).		  │
│ M  │ mountall(8)			│				  │
│ N  │ network-interface job		│				  │
│ O  │ upstart-dconf-bridge(8)		│ See dconf-event(7).		  │
│ R  │ /etc/cron.daily/upstart		│ See cron(8).			  │
│ S  │ upstart-socket-bridge(8)		│ See socket-event(7).		  │
│ T  │ telinit(8), shutdown(8)		│				  │
│ U  │ upstart-udev-bridge(8)		│				  │
│ V  │ System V init system		│				  │
│ X  │ failsafe job			│				  │
└────┴──────────────────────────────────┴─────────────────────────────────┘

Table 5: Event Summary Notes.

┌─────┬─────────────────────────────────────────────────────────────────┐
│Note │ Detail								│
├─────┼─────────────────────────────────────────────────────────────────┤
│ A   │ Requires administrator to press Control-Alt-Delete key combina‐ │
│     │ tion 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 (system or Session Init).				│
│ K   │ 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.							│
│ 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  moun‐ │
│     │ tall(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  suc‐ │
│     │ cessful,  the standard startup(7) event is then emitted, allow‐ │
│     │ ing 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.		│
│ T   │ Only emitted for a graphical session.				│
│ U   │ See file-event(7).						│
│ V   │ This  is  a  pseudo-system  event  emitted  directly   by   the │
│     │ upstart-event-bridge(8).					│
│ W   │ Emitted by Session Init only since bridge not run as system job │
│     │ by default.							│
│ X   │ See socket-event(7).						│
│ Y   │ Used primary by Session Job  /usr/share/upstart/sessions/logro‐ │
│     │ tate.conf.							│
└─────┴─────────────────────────────────────────────────────────────────┘

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-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.

SEE ALSO
       all-swaps(7),   control-alt-delete(7),  dbus-daemon(1),	dbus-event(7),
       dconf-event(7),	 file-event(7),	  filesystem(7),   ifdown(8)   ifup(8)
       init(5),	  init(8),   initctl(8),  keyboard-request(7),	local-filesys‐
       tems(7), mountall(8), mounted(7), mounting(7), power-status-changed(7),
       remote-filesystems(7),	runlevel(7),   shutdown(8),   socket-event(7),
       started(7),   starting(7),   startup(7),	   stopped(7),	  stopping(7),
       telinit(8),	 upstart-dbus-bridge(8),      upstart-dconf-bridge(8),
       upstart-event-bridge(8),			       upstart-file-bridge(8),
       upstart-local-bridge(8),			     upstart-socket-bridge(8),
       upstart-udev-bridge(8), virtual-filesystems(7).

upstart				  2013-12-20		     upstart-events(7)
[top]

List of man pages available for ElementaryOS

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net