upstart is a replacement for the /sbin/init daemon that handles starting of tasks and services during boot, stopping them during shutdown, and supervising them while the system is running.
|Operating Systems||POSIX Linux|
Release Notes: upstart-file-bridge: a new bridge to allow jobs to react to file, directory, and file glob events (create/modify/delete). upstart-monitor: a simple CLI/GUI tool that shows event flows.
Release Notes: This release adds the ability to run with PID >1 to allow Upstart to manage a user session. Running Upstart as a 'Session Init' in this way provides features above and beyond those provided by the original User Jobs, such that the User Job facility has been removed entirely. To migrate from a system using User Jobs, simply ensure the user session is started with 'init --user'. There is a new upstart-event-bridge bridge that proxies system-level events down to Session Inits, allowing user jobs to react to udev events.
Release Notes: Re-exec performance was improved. Issues in the logger with unflushed data were fixed. The re-exec scenario is now handled when requested from within a chroot. A minor serialisation data format change was made for sessions. Extra re-exec tests were added. Jobs running within a chroot now log their output within the chroot. New Restart and GetState D-Bus methods were added. 'telinit u' was changed to use the "Restart" D-Bus method rather than sending SIGTERM to play nicely when busybox(1) is init.
Release Notes: 'telinit u' now performs a stateful re-exec, allowing Upstart to continue to supervise jobs after an upgrade of either itself or any of its dependent libraries. This release adds a dependency on libjson (JSON-C). It adds initramfs-less boot support. It allows tests to work in an sbuild environment. Improved error handling. Fixes a crash if 'kill signal' is specified as a particular numeric. Documentation fixes.
Release Notes: This release adds many "console log" improvements, an "early logging" facility which allows jobs which end before the log disk is writeable to have their output written to disk when the disk later becomes writeable, the ability to detect jobs which leak file descriptors, and a "usage" stanza which allows instance jobs to display a usage message explaining how the job should be started (the usage is displayed when the user has not specified the correct variables to allow the job to be started, or when the user queries the usage using "initctl usage <job>").