10-08-2008
If you have more than 15 minutes to plan for "emergency shut down" of your servers, I'd recommend:
1. All applications that are running have corresponding startup and shutdown scripts in rc.*
2. Identify the order that your hosts should be shutdown in - NIS or LDAP should shutdown last, NFS servers second last... NTP would go first...
3. Write scripts.
You need to send a wall to all users connected informing them of an impending outage.
You need to ensure that you send the right shutdown options to the right OS types.
You need to create for each command that you are sending - for audit and CYA purposes later.
4. Inform your business/clients/users that these are the "emergency shutdown" procedures. Get them to sign-off and buy into them. If they have special requirements, amend your policy to include those.
Ensure that you have adequate time to shutdown storage devices that may have a great deal of data in cache. Ensure that you have adequate time to shutdown tape storage systems, as the robotics may need more time to get to "home" than you might expect.
There is no shortage of things that you could do, but this should get you started.
Last edited by avronius; 10-08-2008 at 03:17 PM..
Reason: Grammer
8 More Discussions You Might Find Interesting
1. SCO
I need to boot an OpenServer 5.0.5 server but I don't have emergency boot disks for it. There are some boot disks of other servers.
Can I use these disks, changing defbootstr ?. How ?.
The fact is that administrator can't login as root and it seems to be a corrupted auth system issue. Other... (2 Replies)
Discussion started by: dags
2 Replies
2. Shell Programming and Scripting
I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies
3. UNIX for Dummies Questions & Answers
I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS).
Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies
4. Ubuntu
Hi guys
i have some question about ubuntu(10.10)
1.what time scheduling & page replacement algorithm have been used in ubuntu
2.how to create a process
3.how to kill a process
4.how to send information to a process
5.how to see a process
6.how to increase priority of a process
7.how to... (1 Reply)
Discussion started by: mortez28
1 Replies
5. Solaris
Hi Guru's,
I am unable to mount NFS share on unix system (DG/UX) which is nfs client.
Error:
mount: /nfsshare: Invalid argument
mount: giving up on:
/mountpoint
i tried following commands
mount -t nfs remotehost:/nfsshare /mountpoint
Error:
mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies
6. Solaris
Dear all,
Kinda lame question but i'd like to hear your experiences and advice.
Question in short
-----------------
What permission should a mount point "ideally" have - i think it's root.
Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies
7. Shell Programming and Scripting
can anyone please tell me that how can i boot unix from a cd? full procedure.
it's an emergency. reply asap (1 Reply)
Discussion started by: niket agarwal
1 Replies
8. Linux
Hello admins and gurus
I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h [-u] | -r | -s | -k] [-o [-n]] time [warning-message ...]
DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving
them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties.
The following options are available:
-h The system is halted at the specified time.
-k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all
but super-user).
-n If the -o is specified, prevent the file system cache from being flushed by passing -n option to halt(8) or reboot(8). This option
should probably not be used.
-o If -h or -r is specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8).
-r The system is rebooted at the specified time.
-s The system is put to sleep at the specified time.
-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.
time Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system val-
ues. The first form brings the system down in number minutes and the second at the absolute time specified.
warning-message
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If '-' is supplied as an option, the warning message is read from the standard input.
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on
the terminals of all users logged in.
At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea-
son. Corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice).
SIGTERM TO SIGKILL INTERVAL
Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally inde-
terminate 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 functionality.
SEE ALSO
kill(1), login(1), wall(1), halt(8), launchd(8), reboot(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 11, 1998 BSD