Sponsored Content
Full Discussion: Bouncing Unix Servers
Operating Systems HP-UX Bouncing Unix Servers Post 302069858 by csaunders on Wednesday 29th of March 2006 04:29:37 PM
Old 03-29-2006
Quote:
Originally Posted by rhfrommn
Where I work now we have a scheduled monthly maintenance window. On a particular Saturday we get to do whatever we need to the boxes. Everybody that uses the systems knows this and nobody works that Saturday.

Our policy is any system which hasn't been rebooted for 90 days is rebooted. Oracle servers and some Veritas Cluster Server clusters are rebooted each month instead. There are a few production boxes exempted from the policy because they support manufacturing plants which have shifts working on Saturdays.

As for the reason why - it is basically just for cleanup purposes. Stale NFS handles, zombie processes, small memory leaks from applications, etc. are all cleaned up by the reboot. Also it is a way of testing to make sure everything runs smoothly with the startup and shutdown scripts so we don't find problems with them when there is an unscheduled reboot.

I've worked other places that never rebooted machines unless it was for a specific purpose - hardware upgrades/repairs, software installs which require it, etc. It all depends on the environment and what the system admins prefer whether a scheduled reboot is appropriate or not.
good god, UNIX=NO REBOOTS, what kind of data center is this....

"Stale NFS handles, zombie processes, small memory leaks from applications, etc. are all cleaned up by the reboot"

the root cause of these should be found, not band-aided by a reboot...

you should never ever reboot unix servers unless you change the kernal or specific uprgrades require it...
 

9 More Discussions You Might Find Interesting

1. SCO

Is ncftp possible between two SCO Unix servers?

Hi. Can entire data be taken thr' ncftp from one SCO Unix server to another? Please let me know. (0 Replies)
Discussion started by: hrishi10a
0 Replies

2. UNIX for Dummies Questions & Answers

Search Files In Unix Servers

hi all! I am VB developer and i am trying to automate a process in UNIX for which i request your help. I want to learn the technique by which we can write batch process in unix server to search for a list of files and to note down files that are missing from the list in the form of a log so... (2 Replies)
Discussion started by: varsai123
2 Replies

3. UNIX for Dummies Questions & Answers

re-associating 2 HP UNIX servers

Hello, i am new to both this forum and UNIX as well; i am working at a local cancer center trying to reassociate 2 UNIX server systems that i am unfamiliar with; Both C3600 workstations were associated, however they were disassociated and need to be reassociated so programs can be accessed on... (0 Replies)
Discussion started by: RarisRSX
0 Replies

4. UNIX for Advanced & Expert Users

MOnitoring Software for Unix servers

Guys, I need a monitoring software for my Unix servers. Over the last couple of years, the number has increased to well over 40 servers. All have different applications running on them and it is impossible to go to everyone of them and do checks. I was using Spotlight on Unix. I was... (1 Reply)
Discussion started by: jair
1 Replies

5. Shell Programming and Scripting

FTP between two UNIX servers

Hi I have server A and server B. On server B the directory is called /tmp/hmp On server A I want to get the files on server B:/tmp/hmp via FTP. After I have got the files via FTP I have to delete them. In the script below I'm affraid of that I delete files before I get them by ftp. ... (1 Reply)
Discussion started by: hpedersen4
1 Replies

6. Shell Programming and Scripting

unix servers

hi, anyone please explain ab the unix servers thanks in advance Satya (2 Replies)
Discussion started by: Satyak
2 Replies

7. Shell Programming and Scripting

Comparing directories on different unix servers

Is it possible to use the diff command to compare two directories on different Unix (AIX) servers? We have two regions set up and we want to be able to compare if the scripts directory in both regions contain the same files? I want to figure out if its possible.. Have been messing around by... (10 Replies)
Discussion started by: Jazmania
10 Replies

8. UNIX for Dummies Questions & Answers

Record count in Unix servers

Hi All, when i ftp the file from windows machine to unix server the record count in the file is decreased by 1. example: Say a text file has three lines in it and when you place this file in unix server from your local machine and run a below command cat filename | wc -l the output is... (2 Replies)
Discussion started by: Umeshrm
2 Replies

9. UNIX for Dummies Questions & Answers

UNIX Servers Syncronization Software

:wall: Does anyone know of a good Unix Server Syncronization Softwarware, I have a customer that has a primary server but he wants to get another one as a backup and he wants to syncronize all the disks on a daily or weekly bases to have it ready in case the primary fails. Your help would be... (2 Replies)
Discussion started by: reb
2 Replies
shutdown(1M)															      shutdown(1M)

NAME
shutdown - terminate all processing SYNOPSIS
[grace] [grace] DESCRIPTION
The command is part of the HP-UX system operation procedures. Its primary function is to terminate all currently running processes in an orderly and cautious manner. can be used to put the system in single-user mode for administrative purposes such as backup or file system consistency checks (see fsck(1M)), to halt or reboot the system, or to make the partition ready for reconfiguration. By default, is an interactive program. Options and Arguments recognizes the following options and arguments. Shut down the system and halt. Shut down the system and reboot automatically. Shut down the system to a ready-to-reconfigure state and reboot if possible. If the partition is unable to reboot, it will stop at a ready-to-reconfigure state. However, if the option is also speci- fied, the system will always stop at ready-to-reconfigure state. This option is available only on systems that support hardware partitions. Shut down the system to a ready-to-reconfigure state and do not reboot. This option can be used only in combination with the option. This option is available only on systems that support hard- ware partitions. Do not require any interactive responses from the user. (Respond or as appropriate to all questions, such that the user does not interact with the shutdown process.) When executed on the cluster in a diskless cluster environment, shutdown the only and do not reboot If this argument is not entered the default behav- ior is to reboot all when the is shutdown. grace Either a decimal integer that specifies the duration in seconds of a grace period for users to log off before the system shuts down, or the word The default is 60. If grace is either 0 or runs more quickly, giving users very little time to log out. If (reboot) or (halt) or (reconfigure) are not specified, and systems are placed in single-user state. Either (reboot) or (halt) must be specified for a shutdown to single-user state is not allowed for a See init(1M). If the optional bundle is installed on the system, the system reboot time may improve for the (reboot), the (halt), and the (reconfigure) options. Shutdown Procedure goes through the following steps: o The environment variable is reset to o The environment variable is reset to space, tab, newline. o The user is checked for authorization to execute the command. Only authorized users can execute the command. See for more information on the authorization file. o The current working directory is changed to the root directory o All file systems' super blocks are updated; see sync(1M). This must be done before rebooting the system to ensure file system integrity. o The real user ID is set to that of the superuser. o A broadcast message is sent to all users currently logged in on the system telling them to log out. The administrator can spec- ify a message at this time; otherwise, a standard warning message is displayed. o The next step depends on whether a system is a or a o If the system is is executed to shut down subsystems, unmount file systems, and perform other tasks to bring the system to run level 0. o If the system is a the optional argument is used to determine if all in the cluster should also be rebooted. The default behavior (command-line parameter is not entered) is to reboot all using entering results in the only being rebooted and the being left alone. Then is executed to shut down subsystems, unmount file systems, and perform other tasks to bring the system to run level 0. o If the system is a is executed to bring the system down to run-level 2, and then is executed. Shutdown to the single-user state is not an allowed option for o The system is rebooted, halted, or put in the ready-to-reconfigure state by executing if the or or option was chosen. If the system was not a cluster client and the system was being brought down to single-user state, a signal is sent to the process to change states (see init(1M)). DIAGNOSTICS
This is the most commonly encountered error diagnostic, and happens when a particular file system could not be unmounted; see mount(1M). User is not authorized to shut down the system. User and system must both be included in the authorization file EXAMPLES
Immediately reboot the system and run HP-UX again: Halt the system in 5 minutes (300 seconds) with no interactive questions and answers: Go to run-level in 10 minutes: Immediately shut down a partition so that it can be deleted: Reboot a partition in 5 minutes so that new cells that have been assigned to the partition become active: WARNINGS
The user name compared with the entry in the file is obtained using (see getpwent(3C)). The hostname in is compared with the hostname obtained using (see gethostent(3N)). must be executed from a directory on the root volume, such as the directory. The maximum broadcast message that can be sent is approximately 970 characters. When executing on an NFS diskless cluster server and the option is not entered, clients of the server will be rebooted. No clients should be individually rebooted or shutdown while the cluster is being shutdown. If the option is used in a virtual partition environment on a partitionable system, then the requested reconfiguration will not take place until all the virtual partitions on that hard partition are shut down and the virtual partition monitor is rebooted. FILES
Authorization file. The file contains lines that consist of a system host name and the login name of a user who is authorized to reboot or halt the system. A superuser's login name must be included in this file in order to execute However, if the file is missing or of zero length, the user can run the program to bring the system down. This file does not affect authorization to bring the system down to single-user state for maintenance purposes; that operation is permitted only when invoked by a superuser. A comment character, at the beginning of a line causes the rest of the line to be ignored (comments cannot span multiple lines without additional comment characters). Blank lines are also ignored. The wildcard character can be used in place of a host name or a user name to specify all hosts or all users, respectively (see hosts.equiv(4)). For example: SEE ALSO
fsck(1M), init(1M), killall(1M), mount(1M), reboot(1M), sync(1M), gethostent(3N), getpwent(3C), hosts.equiv(4). For more information about shutdowns and reboots on Superdome systems, see the manual, available on the web at shutdown(1M)
All times are GMT -4. The time now is 06:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy