Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

reboot(8) [bsd man page]

REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - stopping and restarting the system SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ] /sbin/halt [ -lqndars ] /sbin/fastboot [ -lqndarsRD ] DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is necessary to read it in from disk or tape each time it is to be boot strapped. Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first. Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation. Options to reboot are: -l Don't try to tell syslogd(8) what's about to happen. -q Reboot quickly and ungracefully, without shutting down running processes first. -n Don't sync before rebooting. This can be used if a disk or the processor is on fire. -h Don't reboot, simply halt the processor. -d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic. -a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix). -r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD. -s Don't enter multi-user mode after system has rebooted - stay in single user mode. -f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt) flag. -D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program. -R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the root/swap/pipe/dump device. Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this case. Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively. Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8) 3rd Berkeley Distribution May 24, 1996 REBOOT(8)

Check Out this Related Man Page

reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. Example 1: Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2: Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. 11 Apr 2005 reboot(1M)

Featured Tech Videos