Sponsored Content
Top Forums UNIX for Advanced & Expert Users Solaris shutdown and boot history Post 302459210 by hergp on Monday 4th of October 2010 05:40:07 AM
Old 10-04-2010
Maybe you are lucky with the cron log in /var/cron/log. You can find records like
Code:
! SIGTERM Tue Apr 27 15:35:01 2010
! ******* CRON ABORTED ******** Tue Apr 27 15:35:01 2010
! *** cron started ***   pid = 267 Tue Apr 27 15:38:56 2010

there, which is usually caused by a reboot.
 

10 More Discussions You Might Find Interesting

1. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

2. Solaris

Restart/Shutdown the Solaris from SC>

Hi Experts, I am running solris 9. Sun-Fire 880. How do i shutdowon the whole server using ALOM i.e sc> console. If the server is down or somehow hang How do i Restart from sc> //purple (6 Replies)
Discussion started by: thepurple
6 Replies

3. Infrastructure Monitoring

unable to shutdown solaris 10

hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient. /etc(R)-bash-3.00$ init 6 /etc(R)-bash-3.00$ svc.startd: The system is coming down. Please wait.... (7 Replies)
Discussion started by: alienkidmj12
7 Replies

4. Solaris

Solaris 10 container graceful shutdown?

Hi, I've got a UPS connected to my Solaris 10 machine and I'm planning to run containers/zones on there. At the moment if the UPS agent sends the signal to the solaris machine to shutdown, all the apps shutdown gracefully and then the host goes down. If I setup containers for the apps, does... (9 Replies)
Discussion started by: fastexit
9 Replies

5. Solaris

Remote shutdown Solaris

Hi I want to shutdown my remote Solaris servers from XP machine. i want their must be a script file which i run all of the server go down. i try telnet but it ask for passwd. help me out. (4 Replies)
Discussion started by: akhaliq22
4 Replies

6. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

7. Shell Programming and Scripting

Automatic shutdown and startup of Tomcat in Solaris

Dear Experts , I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command # su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh" but i am getting following error. Please suggest .... (1 Reply)
Discussion started by: Amit.saini333
1 Replies

8. Shell Programming and Scripting

Boot/Shutdown script automation

Looking to automate some commands to run at boot and poweroff in a startup/shutdown script. How do I place it on the system so that it will be run automatically? I don't want to use cron, not quite specific enough, random times when I may boot or shutdown. ---------- Post updated at 10:47 PM... (8 Replies)
Discussion started by: 3therk1ll
8 Replies

9. Red Hat

Boot/Shutdown scripts

Server: Redhat 6.2 Goal: Startup script/Shutdown Script Overview: I'm just doing a very basic test. I'm not getting chkconfig involved. Research so far: I've found a few different ways of getting this to work, some say I can just drop the scripts in the corresponding rc directory. Others... (4 Replies)
Discussion started by: HayekSplosives1
4 Replies

10. Solaris

Solaris stuck during boot after reconfigure boot

Hello, I have a problem with my machine that won't boot properly. The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. 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 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. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -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. 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. 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 /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ 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) 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. 11 Apr 2005 reboot(1M)
All times are GMT -4. The time now is 07:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy