Return to reboot.2 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man2

Annotation of 43BSDTahoe/man/man2/reboot.2, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1980 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)reboot.2    6.1 (Berkeley) 5/9/85
                      6: .\"
                      7: .TH REBOOT 2 "May 9, 1985"
                      8: .UC 4
                      9: .SH NAME
                     10: reboot \- reboot system or halt processor
                     11: .SH SYNOPSIS
                     12: .nf
                     13: .B #include <sys/reboot.h>
                     14: .PP
                     15: .B reboot(howto)
                     16: .B int howto;
                     17: .fi
                     18: .SH DESCRIPTION
                     19: .I Reboot
                     20: reboots the system, and is invoked automatically
                     21: in the event of unrecoverable system failures.
                     22: .I Howto
                     23: is a mask of options passed to the bootstrap program.
                     24: The system call interface permits only RB_HALT or RB_AUTOBOOT
                     25: to be passed to the reboot program; the other flags
                     26: are used in scripts stored on the console storage media, or used
                     27: in manual bootstrap procedures.
                     28: When none of these options (e.g. RB_AUTOBOOT) is given, the system is rebooted
                     29: from file \*(lqvmunix\*(rq in the root file system of unit 0
                     30: of a disk chosen in a processor specific way.
                     31: An automatic consistency check of the disks is then normally performed.
                     32: .PP
                     33: The bits of
                     34: .I howto
                     35: are:
                     36: .TP
                     37: RB_HALT
                     38: the processor is simply halted; no reboot takes place.
                     39: RB_HALT should be used with caution.
                     40: .TP
                     41: RB_ASKNAME
                     42: Interpreted by the bootstrap program itself, causing it to
                     43: inquire as to what file should be booted.  Normally, the system is
                     44: booted from the file \*(lqxx(0,0)vmunix\*(rq without asking.
                     45: .TP
                     46: RB_SINGLE
                     47: Normally, the reboot procedure involves an automatic disk consistency
                     48: check and then multi-user operations.  RB_SINGLE prevents the consistency
                     49: check, rather simply booting the system with a single-user shell on
                     50: the console.
                     51: RB_SINGLE is interpreted by the
                     52: .IR init (8)
                     53: program in the newly booted system.
                     54: This switch is not available from the system call interface.
                     55: .PP
                     56: Only the super-user may
                     57: .I reboot
                     58: a machine.
                     59: .SH "RETURN VALUES"
                     60: If successful, this call never returns.  Otherwise, a \-1
                     61: is returned and an error is returned in the global variable
                     62: .IR errno .
                     63: .SH ERRORS
                     64: .TP 15
                     65: [EPERM]
                     66: The caller is not the super-user.
                     67: .SH "SEE ALSO"
                     68: crash(8), halt(8), init(8), reboot(8)
                     69: .SH BUGS
                     70: The notion of ``console medium'', among other things,
                     71: is specific to the VAX.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.