06-04-2014
How about trying the below
last | grep -i reboot
or if you want to know the shutdown too
last | egrep -i 'reboot|shutdown'
It will give you date, time and terminal.
To do the actual count you can use |wc -l at the end.
Last edited by ibmtech; 06-04-2014 at 01:39 PM..
Reason: Added another line
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Guys,
For the past month, our sun solaris server has rebooted itself 3 times. The sysadmin is saying that is not a sun issue and does not want to carry out any further research with sun about that. The db logfile does not show anything about any db issues at that time. I opened an oracle TAR... (3 Replies)
Discussion started by: mnjanje
3 Replies
2. UNIX for Dummies Questions & Answers
Hi all
i am using sun solaris 2.8 un sunultra10 sparc server.It is our firewall server. with check point firewall running.
but the server suddenly halted several times with the same error as follows....and then there was no option but to reboot.
the error was
panic /thread=0*6115d360... (2 Replies)
Discussion started by: Prafulla
2 Replies
3. UNIX for Dummies Questions & Answers
HP-UX reboots? Time between them?
I have a ? concerning planned reboots of a HPUX 11.11 (RP7410 machine; 10GB RAM; Oracle 8; BaaN v4c4 ERP). My new boss seems to think that all machines (Wintel & UX) should run 24x7x365 and NEVER ever require a reboot. In the practical world we SysAdmins know... (3 Replies)
Discussion started by: bergerp
3 Replies
4. Solaris
i have a sun 280R server , that reboots randomly .
i have checked for hardware failures but none can be seen .
here is the output of prtdiag -v
System Configuration: Sun Microsystems sun4u Sun Fire 280R (2 X UltraSPARC-III
+)
System clock frequency: 150 MHz
Memory size: 2048... (1 Reply)
Discussion started by: ppass
1 Replies
5. Solaris
hello, my problem is the one of the title , as I press enter on Solaris voice in the grub, my computer reboots , is there an option, a flag ,I can add to the Solaris voice , that allow me to see where is the problem ? something that avoid the computer reboot on error? I can't find a way to know... (7 Replies)
Discussion started by: freeware
7 Replies
6. Ubuntu
Hi all,
I am using Ubuntu lucid. It is installed on external USB HDD and I boot into it.
Besides other issues, the most significant one is as follows..
I boot in and start working. Everything goes on fine. As soon as I move the HDD, change its position, etc, all icons tuns into a red... (1 Reply)
Discussion started by: morningSunshine
1 Replies
7. AIX
Am new to AIX please help me. I have AIX7 server. When ever the system reboots my script need to run automatically. This will help me to start my application automatically after the server reboot.
Thanks,
Prince Wells (9 Replies)
Discussion started by: prince1987
9 Replies
8. Solaris
Hi,
I'm in process of creating oracle RAC using Solaris 10 in VirtualBox. I want to know how can I change the ownership of device e.g /dev/rdsk/c0t3d0s0 and keep it persistent during rebbots.
When I enter
chown grid:install /dev/rdsk/c0t3d0s0
ls -l still shows root:root.
Thanks
... (2 Replies)
Discussion started by: jia786
2 Replies
9. Slackware
Hi:
The OS is Slackware 14.0. When, after 14.0 install I first ran alsamixer, I got an error message and it quit. After some googling, I created /etc/modprobe.d/alsa.conf with these lines:
alias snd-card-0 snd_hda_intel
alias sound-slot-0 snd_hda_intel
options snd_hda_intel... (0 Replies)
Discussion started by: stf92
0 Replies
10. HP-UX
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
LEARN ABOUT OPENSOLARIS
systemd-halt.service
SYSTEMD-HALT.SERVICE(8) systemd-halt.service SYSTEMD-HALT.SERVICE(8)
NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic
SYNOPSIS
systemd-halt.service
systemd-poweroff.service
systemd-reboot.service
systemd-kexec.service
/lib/systemd/systemd-shutdown
/lib/systemd/system-shutdown/
DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
to execute the respective actions.
When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
detach all remaining storage devices and kill all remaining processes.
It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
read-only.
Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
finished.
Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
such as "systemctl halt" or suchlike.
SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)
systemd 237 SYSTEMD-HALT.SERVICE(8)