12-22-2011
My experience is that virtual servers need to be rebooted more often than stand alone servers. Here is an example from one stand alone linux server:
Quote:
$ uptime
16:03:28 up 754 days, 8:12, 1 user, load average: 3.34, 3.83, 3.79
Over two years since the last reboot .....
9 More Discussions You Might Find Interesting
1. SCO
Dear sir,
I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this.
Thanks,
Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies
2. Shell Programming and Scripting
I want to get an email alert from a cronjob when a server got rebooted unexpectedly. Please help. Thanks! :confused: (2 Replies)
Discussion started by: angloi
2 Replies
3. UNIX for Advanced & Expert Users
hi all, :)
for a reboot of sun box for patch installation i would like to know where do the reboot logs apart from /var/adm/messages and patch run messages would be available,
i would like to know the sequence of messages logged in the file like
requesting the users to log out
sending a... (1 Reply)
Discussion started by: matrixmadhan
1 Replies
4. AIX
I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server.
I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies
5. Solaris
Hi All,
I want to know the procedure like if server is down, i want to reboot the server through console ($rsc or $sc prompt).Could you please help me out.
I would really appreciate your cooperation.
thanks for understanding
regards
krishna (5 Replies)
Discussion started by: murthy76
5 Replies
6. UNIX for Advanced & Expert Users
Hi,
please could someone advise the best command to shutdown and then for it to reboot back online again.
Note: I shall be doing this from a telent session.
regards
venhart (3 Replies)
Discussion started by: venhart
3 Replies
7. Red Hat
Hi All,
Our Linux server were rebooted 723 days before and now We have decided to reboot the server due to server performance.
Could someone advise us what is the optimal duration of a server reboot ?
Thanks for your time.
Best Regards,
Arun (2 Replies)
Discussion started by: arunap44
2 Replies
8. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
9. Red Hat
Hi,
The server got rebooted and below messages can be seen in /var/log/messages
Sep 7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796}
Sep 7 10:49:12 minersville kernel: <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}... (3 Replies)
Discussion started by: admin_db
3 Replies
uptime(1) General Commands Manual uptime(1)
NAME
uptime, w - show how long system has been up and/or who is logged in and what they are doing
SYNOPSIS
[user]
[pset_list]]
[user]
[pset_list]]
DESCRIPTION
prints the current time, the length of time the system has been up, the number of users logged on to the system, and the average number of
jobs in the run queue over the last 1, 5, and 15 minutes for the active processors.
is linked to and prints the same output as displaying a summary of the current activity on the system.
Options
and recognize the following options:
Print the current time, the length of time the system has been up,
and the number of users logged on to the system in the first line of the output. The average number of jobs in the core over
the last 1, 5, and 15 minutes for the active processors is also printed.
When used with the option, the load averages for the processor sets (psets) are calculated on a core basis.
Suppress the first line and the heading line.
This option should not be used with the option. This option assumes the use of the option to
Use long output.
This option assumes the use of the option to
Print the current time, the length of time the system has been up, and
the number of users logged on to the system in the first line of the output. The load averages over the last 1, 5, and 15
minutes for the processor sets (psets) given in the command line, pset_list, are displayed in the subsequent lines. If no
arguments are given, the load averages are displayed for all the psets in the system.
If pset id of an empty pset is given in the command line, a corresponding message will be displayed. If the kernel does not
have the pset capability, gives an error. The option cannot be used along with other options except
Use the short form of output for displaying terminal information.
The terminal name is abbreviated, and the login time and CPU times are suppressed.
Print only the first line describing the overall state of the system.
This is the default for the command.
Print a summary of the current activity on the system for each user.
This is the default for the command.
EXAMPLES
The command:
produces text resembling the following:
depending upon the current status of the system.
The command:
gives the load average of all the psets in the system. If 0, 94, 95, and 97 are existing psets in the system, the output will look like
the following:
The command:
gives output which looks like the following if 94 and 95 are valid pset ids:
The command:
gives the load average of the system, producing output resembling the following:
The command:
gives the load average of all the psets in the system. If 0 and 1 are psets in the system, the output will look like the following:
AUTHOR
was developed by the University of California, Berkeley and HP.
SEE ALSO
mpctl(2), pset_ctl(2).
uptime(1)