Sponsored Content
Full Discussion: Bouncing Unix Servers
Operating Systems HP-UX Bouncing Unix Servers Post 302070019 by rhfrommn on Thursday 30th of March 2006 02:31:25 PM
Old 03-30-2006
Please let me know where to send my resume. I'd love to work at your datacenter where nothing ever breaks. Smilie

Unfortunately, I'm not in that situation. We have 7 admins responsible for a couple hundred servers and several hundred more workstations. We support well over 1000 users and have automounter maps that allow them to connect to several hundred project directories on a SAN with over 100 TB of storage. And we're responsible for EVERYTHING in the Unix and Storage environment from password resets to desktop linux support to system architecture to filling out purchase orders for new equipment.

In a perfect world I agree with you we'd be able to keep machines up constantly by fixing each problem as it happened. But with the thousands of mounts and unmounts that happen every day we get some stale file handles for example. There are plenty of other little problems that come up which really don't need to be solved immediately that the monthly or 90-day reboot clears up. There is absolutely no way we could spend the time having a system administrator track each of them down individually without double the people. And there is no need for us to do it - for over a decade the monthly maintenance policy has been in place and the business units and users we support agree with it. So we let the minor stuff I mentioned go and clean it up during maintenance by rebooting.

Also, we are in the medical industry so there are very strict regulations about reliability and disaster recovery. Many of our machines are required to be rebooted on a schedule to prove that they are configured properly and will come up correctly after an unplanned outage. For example, the Veritas clusters I mentioned rebooting monthly. Our DR policy requires that to prove the clusters are able to function properly in a failover situation where one system crashes. We actually have to sign and file documents verifying the status of each system after it comes back up. Thus it doesn't matter if we think they need it for a technical reason or not, a lot of those reboots are going to happen to satisfy the policies put on us by the regulatory department.

So I'd finish by pointing out my last paragraph of the original message. It all depends on the environment. Just as you said is the right way to do it, most places I've worked did not have scheduled reboots. However, due to specific factors in the environment I work in now we have to do it. You need to know your users, machines and environment well enough to know what reboot policy is best for your situation.
 

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
reboot(1M)						  System Administration Commands						reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] /usr/sbin/reboot [-f [-e environment]] [-dlnq] [boot_arguments] DESCRIPTION
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. On x86 systems, when the -f flag is specified, the running kernel will load the next kernel into memory, then transfer control to the newly loaded kernel. This form of reboot is shown in the second synopsis, above. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On x86 systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. OPTIONS
The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -e If -f is present, reboot to the specified boot environment. -f Fast reboot, bypassing firmware and boot loader. The new kernel will be loaded into memory by the running kernel, and control will be transferred to the newly loaded kernel. If disk or kernel arguments are specified, they must be specified before other boot arguments. This option is currently available only on x86 systems. See EXAMPLES for details. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. OPERANDS
The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. EXAMPLES
Example 1 Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2 Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix Example 3 Fast Rebooting The following examples use the f option to perform fast reboots. The following command reboots to the same kernel. example# reboot -f The following command reboots to another UFS root disk. example# reboot -f -- '/dev/dsk/c1d0s0' The following command reboots to another ZFS root pool. example# reboot -f -- 'rpool/ROOT/root2' The following command reboots to mykernel on the same disk with -k option. example# reboot -f -- '/platform/i86pc/mykernel/amd64/unix -k' The following command reboots to mykernel off another root disk mounted on /mnt. example# reboot -f -- '/mnt/platform/i86pc/mykernel/amd64/unix -k' The following command reboots to /platform/i86pc/kernel/$ISADIR/unix on another boot environment named second_root. example# reboot -f -e second_root The following command reboots to the same kernel with -kv options. example# reboot -f -- '-kv' FILES
/var/adm/wtmpx login accounting file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) NOTES
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. SunOS 5.11 29 Sep 2008 reboot(1M)
All times are GMT -4. The time now is 01:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy