Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

telinit(8) [centos man page]

TELINIT(8)							      telinit								TELINIT(8)

NAME
telinit - Change SysV runlevel SYNOPSIS
telinit [OPTIONS...] {COMMAND} DESCRIPTION
telinit may be used to change the SysV system runlevel. Since the concept of SysV runlevels is obsolete the runlevel requests will be transparently translated into systemd unit activation requests. OPTIONS
The following options are understood: --help Prints a short help text and exits. --no-wall Do not send wall message before reboot/halt/power-off. The following commands are understood: 0 Power-off the machine. This is translated into an activation request for poweroff.target and is equivalent to systemctl poweroff. 6 Reboot the machine. This is translated into an activation request for reboot.target and is equivalent to systemctl reboot. 2, 3, 4, 5 Change the SysV runlevel. This is translated into an activation request for runlevel2.target, runlevel3.target, ... and is equivalent to systemctl isolate runlevel2.target, systemctl isolate runlevel3.target, ... 1, s, S Change into system rescue mode. This is translated into an activation request for rescue.target and is equivalent to systemctl rescue. q, Q Reload daemon configuration. This is equivalent to systemctl daemon-reload. u, U Serialize state, reexecute daemon and deserialize state again. This is equivalent to systemctl daemon-reexec. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. NOTES
This is a legacy command available for compatibility only. It should not be used anymore, as the concept of runlevels is obsolete. SEE ALSO
systemd(1), systemctl(1), wall(1) systemd 208 TELINIT(8)

Check Out this Related Man Page

RUNLEVEL(8)							     runlevel							       RUNLEVEL(8)

NAME
runlevel - Print previous and current SysV runlevel SYNOPSIS
runlevel [options...] OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters. Table 1. Mapping between runlevels and systemd targets +---------+-------------------+ |Runlevel | Target | +---------+-------------------+ |0 | poweroff.target | +---------+-------------------+ |1 | rescue.target | +---------+-------------------+ |2, 3, 4 | multi-user.target | +---------+-------------------+ |5 | graphical.target | +---------+-------------------+ |6 | reboot.target | +---------+-------------------+ DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known. The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither can be determined, the word "unknown" is printed. Unless overridden in the environment, this will check the utmp database for recent runlevel changes. OPTIONS
The following option is understood: --help Print a short help text and exit. EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise. ENVIRONMENT
$RUNLEVEL If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp. $PREVLEVEL If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp. FILES
/run/utmp The utmp database runlevel reads the previous and current runlevel from. SEE ALSO
systemd(1), systemd.target(5), systemctl(1) systemd 237 RUNLEVEL(8)
Man Page