10-08-2008
emergency shutdown best practices.
Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server?
I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not any money in the budget to upgrade the ups.)
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
LEARN ABOUT REDHAT
upsdrvctl
UPSDRVCTL(8) Network UPS Tools (NUT) UPSDRVCTL(8)
NAME
upsdrvctl - UPS driver controller
SYNOPSIS
upsdrvctl -h
upsdrvctl [-t] [-v] (start | stop | shutdown | status) [ups]
DESCRIPTION
upsdrvctl provides a uniform interface for controlling your UPS drivers. You should use upsdrvctl instead of direct calls to the drivers
whenever possible.
When used properly, upsdrvctl lets you maintain identical startup scripts across multiple systems with different UPS configurations.
OPTIONS
-h Display the help message.
-t Enable testing mode. This also enables verbose mode. Testing mode makes upsdrvctl display the actions it would execute without
actually doing them. Use this to test out your configuration without actually doing anything to your UPS drivers. This may be
helpful when defining the 'sdorder' directive in your ups.conf(5).
-v Enable verbose messages.
COMMANDS
upsdrvctl supports four commands - start, stop, shutdown and status. They take an optional argument which is a UPS name from ups.conf(5).
Without that argument, they operate on every UPS that is currently configured.
start Start the UPS driver(s).
stop Stop the UPS driver(s).
shutdown
Command the UPS driver(s) to run their shutdown sequence. Drivers are stopped according to their sdorder value - see ups.conf(5).
WARNING: this will probably power off your computers, so don't play around with this option. Only use it when your systems are pre-
pared to lose power.
status Check the status of the UPS driver(s).
If every UPS that has been checked is running, then the exitcode will be 0. If one seems to be missing, the exitcode will be 1.
BUGS
The status checking is rudimentary, and really only looks for the presence of .pid files. If you really want to know if your UPS drivers
are alive and well, upsmon(8)'s NOCOMM notifier does a fine job.
SEE ALSO
nutupsdrv(8), upsd(8) ups.conf(5)
Internet resources:
The NUT (Network UPS Tools) home page: http://www.exploits.org/nut/
NUT mailing list archives and information: http://lists.exploits.org/
Wed Oct 16 2002 UPSDRVCTL(8)