Ubuntu's Upstart event-based init daemon


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Ubuntu's Upstart event-based init daemon
# 1  
Old 02-08-2008
Ubuntu's Upstart event-based init daemon

Fri, 08 Feb 2008 09:00:00 GMT
Because the traditional System V init daemon (SysVinit) does not deal well with modern hardware, including hotplug devices, USB hard and flash drives, and network-mounted filesystems, Ubuntu replaced it with the Upstart init daemon.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Red Hat

Upstart initctl

The upstart package that provides initctl command also provides following other commands: start, stop, status etc These commands are all present in /sbin/ in Redhat systems. We can see that status, start, stop, restart are all symlinks to initctl. How do they still work differently? For example... (1 Reply)
Discussion started by: Rameshck
1 Replies

2. News, Links, Events and Announcements

Eulora, a Linux-based MMORPG, holds first game event.

This Sunday, June the 7th, players in attendance will be given unique items engraved with their name. The items can be used to generate free in-game currency on a daily basis, which is particularly notable because the game's currency is bitcoin. I can't post a link yet; if you're interested, engage... (0 Replies)
Discussion started by: danielpbarron
0 Replies

3. Ubuntu

Start Ubuntu without init

Is it possible to start Ubuntu (or any other modern UNIX OS) or get it to any usable state without the init software. By this I mean replacing init with bash and manually initializing all the components. So far i've managed to edit grub at start and get the bash shell but I don't know where... (3 Replies)
Discussion started by: Kadikis
3 Replies

4. Programming

How to init the SPI device in daemon?

I have to make a linux monitoring daemon that works with a SPI device (/dev/spidev). However, I always failed to init this SPI device. The return error code is 25, which means "inappropriate ioctl for device". As I know, daemon runs in background and doesn't have a control terminal and this might... (3 Replies)
Discussion started by: bus147
3 Replies

5. UNIX for Advanced & Expert Users

Unknown event - daemon mode cuts programs from resources

Hi Guys. First of all Im not keen on os stuff, thus not sure what I should look for to solve my problem, Thats why Im posting before getting deeper into forums. Here is my problem. Im working on academic network - Solaris 7-10. Where parts of configuration is made by students (Im still one).... (1 Reply)
Discussion started by: baranowb
1 Replies
Login or Register to Ask a Question
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Upstart process management daemon SYNOPSIS
init [OPTION]... DESCRIPTION
init is the parent of all processes on the system, it is executed by the kernel and is responsible for starting all other processes; it is the parent of all processes whose natural parents have died and it is responsible for reaping those when they die. Processes managed by init are known as jobs and are defined by files in the /etc/init directory. See init(5) for more details on configur- ing Upstart. Events init(8) is an event-based init daemon. This means that jobs will be automatically started and stopped by changes that occur to the system state, including as a result of jobs starting and stopping. This is different to dependency-based init daemons which start a specified set of goal jobs, and resolve the order in which they should be started and other jobs required by iterating their dependencies. For more information on starting and stopping jobs, as well as emitting events that will automatically start and stop jobs, see the manual page for the initctl(8) tool. The primary event is the startup(7) event, emitted when the daemon has finished loading its configuration. Other useful events are the starting(7), started(7), stopping(7) and stopped(7) events emitted as jobs change state. See upstart-events(7) for a summary of well-known events. System V compatibility The Upstart init(8) daemon does not keep track of runlevels itself, instead they are implemented entirely by its userspace tools. The event emitted to signify a change of runlevel is the runlevel(7) event. For more information see its manual page. OPTIONS
Options are passed to init(8) by placing them on the kernel command-line. --confdir directory Read job configuration files from a directory other than /etc/init. --no-sessions Disable user and chroot sessions. --no-startup-event Suppress emission of the initial startup event. This option should only be used for testing since it will stop the init(8) daemon from starting any jobs automatically. --session Connect to the D-Bus session bus. This should only be used for testing. --startup-event event Specify a different initial startup event from the standard startup(7). --verbose Outputs verbose messages about job state changes and event emissions to the system console or log, useful for debugging boot. NOTES
init is not normally executed by a user process, and expects to have a process id of 1. If this is not the case, it will actually execute telinit(8) and pass all arguments to that. See that manual page for further details. FILES
/etc/init.conf /etc/init/*.conf $HOME/.init/ AUTHOR
Written by Scott James Remnant <scott@netsplit.com> REPORTING BUGS
Report bugs at <https://launchpad.net/upstart/+bugs> COPYRIGHT
Copyright (C) 2009-2011 Canonical Ltd. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. SEE ALSO
control-alt-delete(7) init(5) initctl(8) runlevel(7) startup(7) starting(7) started(7) stopping(7) stopped(7) telinit(8) upstart-events(7) Upstart 2011-04-06 init(8)