01-15-2004
the final message should be something like
"system halted"
i am not sure how much of a difference it makes, but shutdown wants the argument first, then time, ie:
shutdown -h +4
however if you use -t to specify amount of seconds until shutdown, then -t comes before desired action, -h.
try it with -h first.
shutdown -h +3
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm in the process of installing openbsd 3.2, the install appears to go ok but will not boot. So I tried the install again, when I opt to partition I noticed the disk the signature (in geometry) reads as 0x0 instead of 0xAA55. I'm using Lucas's 'Absolute OpenBSD' as my install guide together with... (3 Replies)
Discussion started by: ferret
3 Replies
2. BSD
for all you unix/linux interested heres an online book for free that covers the basics of BSD SysV Unix commands and applications . giving the average linux user a perspective on the differences in context of the two operating systems and for BSD users covers material as a refernce guide.
... (0 Replies)
Discussion started by: moxxx68
0 Replies
3. BSD
Hello!
Some time ago I did something stupid, I bought 4 harddisk cases (sata -> USB) without checking enough if it is supported by my choise of OS.
I was thinking of using FreeBSD on my new NAS (a sunblade 100), but after discovering that is didn't work, I started to search for information.
I... (2 Replies)
Discussion started by: noratx
2 Replies
4. AIX
Hi,
I am getting the error "/etc/rc.shutdown failed. Shutdown aborting" while shutting down the os.
Please suggest. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
5. Shell Programming and Scripting
While tomcat shutting down getting the below error.
Error occurred during initialization of VM
Could not reserve enough space for code cache
CATALINA_OPTS="-verbose:gc -Xloggc:gc.log -XX:+PrintGCDetails -XX:MaxPermSize=24M -Xms256M -Xmx512M -Djava.awt.headless=true -XX:-UseCompressedOops... (2 Replies)
Discussion started by: tuxslonik
2 Replies
LEARN ABOUT MOJAVE
reboot
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
halt, reboot -- stopping and restarting the system
SYNOPSIS
halt [-lnqu]
reboot [-lnq]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the wtmp(5) file.
When the system is halted with the halt command, the system is powered off.
The options are as follows:
-l The halt or reboot is not recorded in the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SIGTERM TO SIGKILL INTERVAL
The SIGKILL will follow the SIGTERM by an intentionally indeterminate period of time. Programs are expected to take only enough time to
flush all dirty data and exit. Developers are encouraged to file a bug with the OS vendor, should they encounter an issue with this func-
tionality.
SEE ALSO
wtmp(5), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
June 9, 1993 BSD