01-28-2009
Quote:
Originally Posted by
zaxxon
Reboots are documented in the errpt. You can be lucky and find with errpt -a which uid issued the reboot.
Thanks Zaxxon.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
Since server is located at remote place so how to identify which user rebooted the server. Is there any way to identify the user.
Thanks in advance,
Reg,
Bache Gowda (1 Reply)
Discussion started by: bache_gowda
1 Replies
2. Solaris
Hi,
how can i know who has rebooted the server? even last command is not displaying the user, wheather any way to track the user. (2 Replies)
Discussion started by: manoj.solaris
2 Replies
3. HP-UX
Hi ,
Plz some one can help me ...
How can we know that the server was rebooted by which user in hp unix and linux.
Regards
Venkata Jeevan (1 Reply)
Discussion started by: jeevanbv
1 Replies
4. AIX
Is there such location or command to know how many times did you reboot your server in that particular day?in AIX. (3 Replies)
Discussion started by: kenshinhimura
3 Replies
5. Linux
supermicro(dual core) server getting rebooted after "decompressing the kernel;booting the kernel" message comes.
I tried giving acpi=off to the kernel command line but same problem.It shows everything ok and no problem with memory and processors and power supplies.Wt could be the reason?
It has... (1 Reply)
Discussion started by: pankajd
1 Replies
6. Solaris
In Windows we can check the event viewer for entries 6005,6006,6009 to confirm the system down times, as in when it got down and when it came back up. Is there some similar log files in Solaris/RHEL that I can check the timings and who or what caused the system reboot. I am an absolute newbie. Need... (4 Replies)
Discussion started by: lubu
4 Replies
7. Red Hat
I am trying to figure out what might causing Production server unexpectedly reboot during last few months ..
Is auto reboot is set , I can check it is not set during the kernel panic but are they any other parameters which I am missing .
-bash-2.05b$ uname -a
Linux PD1011... (4 Replies)
Discussion started by: dba1981
4 Replies
8. Red Hat
Hi
One of our server is showing the uptime 0hr 5mints
there is no log in /var/log/messages
there is no log in command "last"
kernel version is 2.4.9 (RH2.1 AS)
What could be the reason for this. is this issue is related to uptime counter reached max
how to verify this.
Best Regards
KVK (4 Replies)
Discussion started by: venikathir
4 Replies
9. Red Hat
Hi,
Yesterday one of Red Hat Server 4.2 got rebooted.
I have checked /var/log/messages, but does not find out any serious issue related to peformance / hardware issue.
how to find out why server was rebooted? (1 Reply)
Discussion started by: manoj.solaris
1 Replies
10. UNIX for Dummies Questions & Answers
I have been mounting a directory to share with a windows pc. If i reboot the AIX box the mount goes away. How can i make the mount permanent? Here is the command I use to make the mount
exportfs -i -o root=<servername> /path (1 Reply)
Discussion started by: fierfek
1 Replies
uadmin(2) System Calls Manual uadmin(2)
NAME
uadmin - provides administrative control
SYNOPSIS
#include <sys/uadmin.h>
int uadmin(
int cmd,
int fcn,
int mdep );
PARAMETERS
Specifies the type of administrative action to be performed on the system. Specifies the type of action to perform after the system is
shutdown or stopped using A_SHUTDOWN or A_REBOOT.
The available actions are AD_HALT, AD_BOOT, or AD_IBOOT. These are described in more detail below. Specifies machine-dependent
use. It is currently not used and is ignored if defined.
DESCRIPTION
The uadmin function enables control of some basic administrative functions. Mostly, it is called by other system administrative procedures
which must perform automatic shutdowns, halts, and reboots of the system. Using this function as a general interface is not recommended.
To perform a shutdown, halt, or reboot of the system, you must use the cmd parameter which specifies the function to be performed. The val-
ues for the cmd parameter are as follows: Signals that the system stop immediately without any further processing. The operation to be per-
formed next is specified by the fcn parameter. Specifies a remount of the root file system after errors have been resolved. This command
should only be used during the startup process. For this release, this command is unsupported. See the RESTRICTIONS section for more
information. Specifies a systematic shutdown of the system by terminating all user processes, flushing the buffer cache, and unmounting
the root file system. The operation to be performed next must be specified by the fcn parameter.
The fcn parameter specifies the operation that is to be performed after the system has been shutdown or rebooted using the A_SHUTDOWN or
A_REBOOT commands. The fcn parameter has the following values: Halts the processor. The machine is then in a state where power can be
turned off. Reboots the system in standalone mode using the default kernel. Reboots the system in interactive mode. You must provide the
kernel name upon a reboot of the machine.
RESTRICTIONS
Specifying A_REMOUNT is not supported for this release. If it is specified, a value of -1 is returned and errno is set to ENOSYS.
RETURN VALUES
On success, specifying either A_SHUTDOWN or A_REBOOT does not return a value. Specifying A_REMOUNT returns zero (0) on success.
On error, a value of -1 is returned and errno is set to indicate error.
ERRORS
Indicates that a command was specified that is invalid.
uadmin(2)