Unix and Linux Discussions Tagged with reboot |
|
Thread / Thread Starter |
Last Post |
Replies |
Views |
Forum |
|
|
|
4 |
5,378 |
UNIX for Beginners Questions & Answers |
|
|
|
3 |
6,314 |
Shell Programming and Scripting |
|
|
|
1 |
9,006 |
UNIX for Beginners Questions & Answers |
|
|
|
2 |
4,531 |
Shell Programming and Scripting |
|
|
|
3 |
1,202 |
Shell Programming and Scripting |
|
|
|
3 |
1,836 |
Shell Programming and Scripting |
|
|
|
13 |
6,958 |
AIX |
|
|
|
4 |
7,824 |
AIX |
|
|
|
2 |
5,181 |
HP-UX |
|
|
|
11 |
11,849 |
Debian |
|
|
|
5 |
5,868 |
Solaris |
|
|
|
6 |
6,687 |
AIX |
|
|
|
1 |
2,220 |
UNIX for Dummies Questions & Answers |
|
|
|
9 |
7,803 |
Solaris |
|
|
|
6 |
5,934 |
Solaris |
|
|
|
14 |
21,838 |
Solaris |
|
|
|
8 |
11,674 |
Linux |
|
|
|
1 |
3,286 |
HP-UX |
|
|
|
2 |
25,758 |
Windows & DOS: Issues & Discussions |
|
|
|
8 |
19,063 |
UNIX for Advanced & Expert Users |
|
|
|
3 |
9,060 |
Solaris |
|
|
|
6 |
7,053 |
AIX |
|
|
|
6 |
9,825 |
UNIX for Dummies Questions & Answers |
|
|
|
3 |
151,571 |
SuSE |
|
|
|
0 |
2,103 |
UNIX for Dummies Questions & Answers |
|
|
|
2 |
12,934 |
Programming |
|
|
|
11 |
10,094 |
Solaris |
|
|
|
0 |
5,481 |
Solaris |
|
|
|
5 |
10,273 |
Solaris |
|
|
|
6 |
8,624 |
Shell Programming and Scripting |
|
|
|
0 |
1,609 |
UNIX and Linux RSS News |
|
|
|
1 |
2,805 |
Solaris |
|
|
|
1 |
3,384 |
AIX |
|
|
|
2 |
4,639 |
Linux |
|
|
|
1 |
6,593 |
Ubuntu |
|
|
|
2 |
3,158 |
Shell Programming and Scripting |
|
|
|
4 |
5,790 |
UNIX for Advanced & Expert Users |
|
|
|
1 |
11,533 |
AIX |
|
|
|
3 |
30,035 |
AIX |
|
|
|
4 |
36,998 |
Solaris |
reboot(8) System Manager's Manual reboot(8)
Name
reboot - automatic reboot procedures
Syntax
/etc/reboot [ -n ] [ -q ]
Description
The ULTRIX system is booted by loading a kernel image, usually into memory at location zero and transferring to zero. Because the system
is not reenterable, the kernel image must be read in from disk each time the system is bootstrapped.
When the reboot of a running system is desired, is normally used. If there are no users, can be used. The command causes the disks to be
synced, and then a multiuser reboot is initiated. The system is booted and an automatic disk check is performed. If the procedure suc-
ceeds, the system is then brought up for the users.
The system will reboot itself after a power failure or after a crash, provided auto-restart is enabled on your system. A consistency check
of the file systems will be performed and, unless the check fails, the system will resume multiuser operations.
Options
-n Prevents the disks from being synced.
-q Reboots quickly and ungracefully, without shutting down running processes first.
Files
System code
See Also
crash(8v), fsck(8), halt(8), init(8), newfs(8), rc(8), shutdown(8)
reboot(8)