Fedora currently uses Upstart 0.3.11. We would like to move to the 0.6 series, which is the currently maintained upstream release. It introduces a few changes to the way Upstart works and is a stepping stone to the more radical 1.0 release. This release is expected to be forward compatible, and also cures some stability problems.
This will also be the first release of Upstart that Fedora has carried which communicates via DBus.
- Name: Petr Lautrbach
- email: <email@example.com>
- Name: Casey Dahlin
- email: <firstname.lastname@example.org>
- Name: Bill Nottingham
- email: <email@example.com>
- Targeted release: Fedora 13
- Last updated: 2010-03-22
- Percentage of completion: 100%
Upstart is an event-based replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running.
- Tasks and Services are started and stopped by events;
- Events are generated as tasks and services are started and stopped;
- Events may be received from any other process on the system;
- Services may be respawned if they die unexpectedly;
- Supervision and respawning of daemons which separate from their parent process;
- Communication with the init daemon over D-Bus.
Benefit to Fedora
The latest upstream Upstart version is 0.6.0 and upstream is pushing to have all the major distros move to the 0.6 series. The new release fixes a lot of bugs, strengthens some of the code patterns against future bugs, and introduces a job format that will continue to be supported through 1.0.
We've carried a patch so that Upstart does not forget its state when it is re-executed. Its got some issues, but it has fixed one or two severe issues. A new version of this has to be written for 0.6; alternatively, we need to change how we re-execute init. We have done the latter for now.
Job definitions are now in a new location (/etc/init rather than /etc/events.d) and the format has changed somewhat, see init(5). We'll need to update our own init scripts to account for this. See the upstart 0.6.0 branch of initscripts.
The list of packages that ship job definitions is:
- initscripts - DONE
- upstart - DONE
- vpnc - DONE
- ConsoleKit - DONE
- clamav - DONE
- dhcp-forwarder - DONE
- hdapsd - DONE
- ip-sentinel - DONE
- milter-greylist - DONE
- olpc-utils - DONE
- readahead - DONE
- tor - DONE
Non-root users get strange output when they run initctl which tries to get information from system dbus - fixed in upstart-0.6.3-7
$ initctl list initctl: Name "com.ubuntu.Upstart" does not exist
How To Test
- Update upstart and initscripts packages: repo here
- rename (or merge your changes) all new /etc/init/*.conf.rpmnew files to /etc/init/*.conf
# kill 1 # reboot
kill 1 is needed if you upgrade from upstart-0.3.x. Control interface has been changed in upstart-0.6 so you won't be able to control old init with new utilities.
- Bring each upstart job up and down and verify that the job is started and cleaned up correctly and that initctl list reflects its state.
- Move from runlevel s to 1, 3, and 5 and back again and verify that the system ends up in the correct state each time.
- Re-exec init and verify that jobs that were running stay running according to initctl list.
Possibly some changes in command interfaces like initctl, but for most users noticing the change would be a Bad Thing.
- init: transfer state across re-exec - https://bugs.launchpad.net/upstart/+bug/348455
- initscripts: changes to support new job format. Also move job definitions to new location
Just don't ship it :) 0.3 should be relatively supported for some time given its presence in Ubuntu LTS.
Nothing needed from Fedora specifically, but the new Upstart release does come with a whole new set of manpages.
"Upstart, Fedora's service management and system initialization daemon, has been upgraded to 0.6.0. If you have been using custom Upstart jobs, they will not work until moved to the new location in /etc/init and ported to the new format."
Comments and Discussion