01-14-2006
Sun has two shutdown commands. The UCB shutdown is a dangerous c program that does do some logging. The real shutdown command is shell script and I don't see any logging there.
I came from an HP-UX environment. On HP-UX, using init to shutdown is like pulling the plug. I got real used to the shutdown command. This is one of the reasons Sun admins have a rough time with HP-UX. They usually manage one shutdown via the init command... although they never do it again. This also may explain why Sun recommends using init!
On Suns, I use the shutdown command because it warns the users... including making an attempt at warning nfs clients. I try to give 5 - 10 minutes warnings. I can abort the shutdown if someone calls. This whole warning stuff gives me some political cover.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i accedently "deleted" all workspaces
I have a black screen and dont know what to do
solaris common desktop enviroment (1 Reply)
Discussion started by: ssshakir
1 Replies
2. Solaris
I need help please .......
I have to urgently setup nvalias 's cdrom .......
following are the output command ......................
{7} ok banner
Sun Fire 3800
OpenFirmware version 5.15.2 (08/04/03 10:27)
Copyright 2001-2003 Sun Microsystems, Inc. All rights reserved.
Use is... (1 Reply)
Discussion started by: tt155
1 Replies
3. Solaris
Hi .....
My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command
after reboot :
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies
4. Shell Programming and Scripting
Hi,
I have written the following UNIX for HP-UX 11i. The script basically checks for files older then 45mins in 2 repective directories and then sends and email to the administrator about them.
Problem with the script is that I can run it from the command line and crontabtab but 80% of the... (2 Replies)
Discussion started by: budrito
2 Replies
5. UNIX for Dummies Questions & Answers
Hi, i have sco openserver 5.0.6 but have a problem with shutdown or reboot commands.
The string I use is "shutdown -g0 -y" but the system just hangs on "The sytem is down" . I used to get a "Safe to turn of" but now nothing. Same with "reboot" the sytem just freezes.
Any suggestions? (1 Reply)
Discussion started by: VTechman
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I am facing a connection problem with Oracle 10g on Solaris 10 when my application (started by /etc/rc3.d at node reboot) tries to establish a session after reboot of the node where my application is running (NCR UNIX (MP RAS)).
I find that my application (run as a deamon process)... (1 Reply)
Discussion started by: sowjanya
1 Replies
7. HP-UX
I have a make_recovery tape, if I restore the VG00 volume group using this, will my other volume groups still be ok after the restore(I have 7 data volume groups)
I used make_recovery -A to create the tape
I have a HP9000 HP-UX 11
An internal disk is failing, the other volume groups are on... (3 Replies)
Discussion started by: rees_a
3 Replies
8. Linux
I have a linux server,in this i receive alarm as server has rebooted.
When i check uptime of the server it says that the server has rebooted but when i check output of who -b it says that the server rebooted very long back
Can some one help what is the issue here. (3 Replies)
Discussion started by: tiwsaj
3 Replies
9. Red Hat
Hi,
I have added 30 GB Vmware Scsci disk in RHEL
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.3 (Tikanga)
I want to make this 30 GB visible to OS without reboot.
Pls help (1 Reply)
Discussion started by: saurabh84g
1 Replies
10. Solaris
Hi All, I am trying to aggregate the NIC's,(igb2 and igb3) (igb0 is used by the physical system and igb1 is used by primary-vsw0) to create the domains on that for faster data transfer, I followed the process for creating the aggregation, dladm create-aggr -d igb2 -d igb3 1
after creating the... (2 Replies)
Discussion started by: buildscm
2 Replies
LEARN ABOUT ULTRIX
shutdown
shutdown(8) System Manager's Manual shutdown(8)
Name
shutdown - close down the system at a given time
Syntax
/etc/shutdown [ -k ] [ -r ] [ -h ] [ -o ] time [ warning-message ... ]
Description
The command provides an automated shutdown procedure that a superuser can use to notify users when the system is shutting down.
The time is the time at which will bring the system down. It may be the word `now', indicating an immediate shutdown, or specify a future
time in one of two formats: + number or hour : min. The first form brings the system down in number minutes. The second brings the system
down at the time of day indicated, using a 24-hour clock format.
At intervals which get shorter as shutdown nears, warning messages are displayed at the terminals of all users on the system. Warning mes-
sages are also sent to users who are logged in to a remote system that has mounted a file system or directory from the local system using
NFS. Five minutes before shutdown, or immediately if shutdown is timed for less than five minutes, logins are disabled by creating and
writing a message there. If this file exists when a user attempts to log in, prints its contents and exits. The file is removed just
before exits.
At shutdown time, a message is written in the file This message contains the time of shutdown, who ran shutdown, and the reason. Then, a
terminate signal is sent at to bring the system to single-user state.
If the or options are used, then executes or avoids shutting the system down (respectively). The option is for use by only. It indicates
to that it is being called by and not to return to the user.
You should place the time of the shutdown and the warning message in Use the message to inform the users about when the system will be back
up and why it is going down.
Restrictions
You can kill the system only between now and 23:59, if you use the absolute time for shutdown.
Files
Tells login not to let anyone log in
Log file for successful shutdowns
See Also
login(1), wall(1), halt(8), opser(8), reboot(8), rwalld(8c)
shutdown(8)