|This article needs additional citations for verification. (August 2010)|
The term runlevel refers to a mode of operation in one of the computer operating systems that implement Unix System V-style initialization. Conventionally, seven runlevels exist, numbered from zero to six; though up to ten, from zero to nine, may be used. S is sometimes used as a synonym for one of the levels. Only one "runlevel" is executed on bootup - run levels are not executed sequentially, i.e. either runlevel 2 OR 3 OR 4 is executed, not 2 then 3 then 4.
"Runlevel" defines the state of the machine after boot. Different runlevels are typically assigned to:
- single-user mode
- multi-user mode without network services started
- multi-user mode with network services started
- system shutdown
- system reboot
The exact setup of these configurations will vary from OS to OS, and from one Linux distribution to another. For example, runlevel 4 might be multi-user, GUI, no-server on one distribution, and nothing on another. Note the difference in the Red Hat and Slackware distributions charted in this article. However, "runlevels" do commonly follow patterns described in this article. It is best to consult the particular distribution's available user guides.
In standard practice, when a computer enters runlevel zero, it halts, and when it enters runlevel six, it reboots. The intermediate runlevels (1-5) differ in terms of which drives are mounted, and which network services are started. Default runlevels are typically 3, 4, or 5. Lower run levels are useful for maintenance or emergency repairs, since they usually don't offer any network services at all. The particular details of runlevel configuration differ widely among operating systems, and also among system administrators.
- 1 Standard runlevels
- 2 Linux
- 3 Unix
- 4 See also
- 5 External links
- 6 References
|0||JNB||Shuts down the system.|
|S||Single user mode||Does not configure network interfaces or start daemons.|
|6||Reboot||Reboots the system.|
^ = Almost all systems use runlevel 1 for this purpose. This mode is intended to provide a safe environment to perform system maintenance. Originally this runlevel provided a single terminal (console) interface running a root login shell. The increasing trend towards physical access to the computer during the boot process has led to changes in this area.
The Linux operating system can make use of runlevels through the programs of the sysvinit project. After the Linux kernel has booted, the init program reads the /etc/inittab file to determine the behavior for each runlevel. Unless the user specifies another value as a kernel boot parameter, the system will attempt to enter (start) the default runlevel.
Linux Standard Base specification
Systems conforming to the Linux Standard Base (LSB) need not provide the exact run levels given here or give them the meanings described here, and may map any level described here to a different level which provides the equivalent functionality.
|0||Halt||Shuts down the system.|
|1||Single-user Mode||Mode for administrative tasks.|
|2||Multi-user Mode||Does not configure network interfaces and does not export networks services.|
|3||Multi-user Mode with Networking||Starts the system normally.|
|4||Not used/User-definable||For special purposes.|
|5||Start the system normally with appropriate display manager. ( with GUI )||Same as runlevel 3 + display manager.|
|6||Reboot||Reboots the system.|
^ = The additional behavior of runlevel 1 varies greatly. All distributions provide at least one virtual terminal. Some distributions start a login shell as the superuser; some require correctly entering the superuser's password; others provide a login prompt, allowing access to any registered user.
^ = In some cases, runlevels 2 and 3 function identically; offering a Multi-user Mode with Networking.
Debian, as well as most of the distributions based on it, does not make any distinction between runlevels 2 to 5.
|S||Only run on boot (replaces /etc/rc.boot)|
|2-5||Full Multi-user with console logins and display manager if installed|
Ubuntu 6.10 (Edgy Eft) and later contain Upstart as a replacement for the traditional init-process, but they still use the traditional init scripts and Upstart's SysV-rc compatibility tools to start most services and emulate runlevels.
|2||Graphical multi-user with networking|
|3-5||Unused but configured the same as runlevel 2|
Red Hat Linux and Fedora
|1||Single-user text mode (without networking)|
|2||Not used (user-definable)|
|3||Full multi-user text mode|
|4||Not used (user-definable)|
|5||Full multi-user graphical mode (with an X-based login screen)|
SUSE uses a similar setup to Red Hat:
|1 or S||Single-user mode|
|2||Multi-user mode without networking|
|3||Multi-user mode, console logins only|
|5||Multi-user mode with display manager|
Slackware Linux uses runlevel 1 for maintenance, as on other Linux distributions; runlevels 2, 3 and 5 identically configured for a console (with all services active); and runlevel 4 adds the X Window System.
|2||Unused but configured the same as runlevel 3|
|3||Multi-user mode without display manager|
|4||Multi-user mode with display manager|
|5||Unused but configured the same as runlevel 3|
|1 or S||Single-user mode|
|2||Multi-user mode without networking|
|4||Aliased for runlevel 3|
|5||Aliased for runlevel 3|
System V Releases 3 and 4
|0||Shut down system, power-off if hardware supports it (only available from the console)|
|1||Single-user mode, all filesystems unmounted but not root, all processes except console processes killed|
|3||Multi-user mode with RFS (and NFS in Release 4) filesystems exported|
|5||Halt the operating system, go to firmware|
|s, S||Identical to 1, except current terminal acts as the system console|
Starting from Solaris 10, SMF (Service Management Facility) is used instead of SVR4 run levels. The latter are emulated to preserve compatibility with legacy startup scripts.
|0||Operating system halted; (SPARC only) drop to OpenBoot prompt|
|S||Single-user mode with only root filesystem mounted (as read-only) -- Solaris 10+: svc:/milestone/single-user|
|1||Single-user mode with all local filesystems mounted (read-write)|
|2||Multi-user mode with most daemons started – Solaris 10+: svc:/milestone/multi-user|
|3||Multi-user mode; identical to 2 (runlevel 3 runs both /sbin/rc2 and /sbin/rc3), with filesystems exported, plus some other network services started. -- Solaris 10+: svc:/milestone/multi-user-server|
|4||Alternative Multi-user mode, User-definable|
|5||Shut down, power-off if hardware supports it|
|S||Single-user mode, booted to system console only, with only root filesystem mounted (as read-only)|
|s||Single-user mode, identical to S except the current terminal acts as the system console|
|1||Single-user mode with local filesystems mounted (read-write)|
|2||Multi-user mode with most daemons started and Common Desktop Environment launched|
|3||Identical to runlevel 2 with NFS exported|
|4||Multi-user mode with VUE started instead of CDE|
|5, 6||Not used/User-definable|
FreeBSD, OpenBSD and NetBSD
The BSD variants don't use the concept of run levels, although on some versions init(8) provides an emulation of some of the common run levels. But invoking init with values below will produce results e.g.,
# init 0
will halt the system
also the init utility will do the above, if sent the user defined signal 2 (USR2).
# kill -USR2 1
as init is always pid 1.
Run-level Signal Action
0 SIGUSR2 Halt and turn the power off 1 SIGTERM Go to single-user mode 6 SIGINT Reboot the machine c SIGTSTP Block further logins q SIGHUP Rescan the ttys(5) file
AIX does not follow the System V R4 (SVR4) run level specification, with run levels from 0 to 9 available, as well as from a to c. 0 and 1 are reserved, 2 is the default normal multi-user mode and run levels from 3 to 9 are free to be defined by the administrator. Run levels from a to c allow the execution of processes in that run level without killing processes started in another.
|2||Normal Multi-user mode||default mode|
- Runlevel Definition - by The Linux Information Project (LINFO)
- What are run levels? - LinuxQuestions.org
- "Chapter 20. System Initialization 20.5. Run Levels". Linux Standard Base Core Specification 4.1. 2011. Retrieved 2011-04-21.
- "Chapter 15. Commands and Utilities 15.2. Command Behavior". Linux Standard Base Core Specification 4.1. 2011. Retrieved 2011-04-21.
- "Debian Linux Runlevels". Retrieved 2013-06-11.
- "Ubuntu Runlevels (Upstart)". Retrieved 2013-06-11.
- "Red Hat SysV init runlevels". Red Hat Enterprise Linux 3 Reference Guide. 2003. Retrieved 2013-05-22.
- Ghori, Asghar (2009). Red Hat Certified Technician & Engineer: Training Guide and Administrator's Reference. La Vergne, Tennessee: Red Hat, Inc. p. 319. ISBN 9781615844302. Retrieved 2014-02-27. "The chkconfig command gives you the ability to display service start and stop settings, and set a service to start and stop at appropriate rc levels."
- Smith, Roderick W. (2011). LPIC-1: Linux Professional Institute Certification Study Guide: (Exams 101 and 102) (2 ed.). John Wiley & Sons. p. 239. ISBN 9781118059715. Retrieved 2014-02-27. "The SysV startup scripts in the runlevel directories are symbolic links back to the original script. [...] Numerous utility programs are available to help you manage these links, such as
rc-update. [...T]he first two of these tools [...a]re supported on most distributions."
- Brown, Chris (2009). SUSE Linux. O'Reilly Media, Inc. p. 231. ISBN 9780596553623. Retrieved 2013-10-07. "The unimaginatively named utility chkconfig can be used to manipulate and interrogate the Slinks and Klinks from the command line."
- "Slackware Linux Runlevels". Retrieved 2013-06-11.
- "Gentoo Linux Runlevels". Retrieved 2013-06-11.
- "Solaris Boot Process". Amrita Sadhukhan (Sun). Retrieved 2009-08-19.