Sponsored Content
Operating Systems Solaris 11.2 not shutting down completely Post 302947219 by gandolf989 on Tuesday 16th of June 2015 12:21:22 PM
Old 06-16-2015
Quote:
Originally Posted by userx-bw
No windows on this laptop, Just Linux and a copy of Solaris 11.2 that is sitting dormant right now.

When I installed it. It took completely over the system. the grub they used made user of that. Unknown to me they are just like Windows in the "its only me" way of life when it comes to using there system. (even though one has to jump through hoops to get it to dual boot)


The HDD on this laptop is ext4 format other then what Solaris made its partition.

Right now I am using Linux on here, with Solaris not being used or in any kind of set up to be used. until I find time to mess with that Grub thing and figure out how to boot into Linux too with it. Grub2 makes things harder too in my option as I my knowledge base about these things is still in a learning pattern.

As far as Solaris shutting down it is like a fresh install on a bare system. So what it did to make it put itself into a wait state or what ever it is in because I cannot see a screen telling me what it is really doing just that splash shutdown screen with the red line that hangs when it gets to a point about 10 to 20 % LEFT TO DO.

I did notice it takes for ever to boot up too, Linux is much faster. Even Windows I fear is faster at boot up time and shut down time even than Solaris is.

I'll look in to this when I find time again.

thanks for your help...
Take a look at your shutdown script and see if it is doing a normal shutdown that does not kill user sessions as a part of the shutdown. You will probably see a /etc/rc0.d/K01dbora linked file that points to your /etc/init.d/dbora file.

You can also manually stop your database the next time you shutdown and if that doesn't do it it must be something else. Have you tried to fsck your file system?

 

10 More Discussions You Might Find Interesting

1. Solaris

shutting down oracle with the server

What can I do to ensure that oracle database is shut down when the server reboots. (1 Reply)
Discussion started by: krishan
1 Replies

2. UNIX for Advanced & Expert Users

Shutting down Solaris

Hi I have a mix of solaris 8,9 & 10. I need to have our 6 Solaris servers shutdown buy a script that will be executed by APC network Shutdown software Im really not sure how I would write a script to shut them down and the following processes? the processes are portmapper seq seq_api... (1 Reply)
Discussion started by: tonysequoia
1 Replies

3. UNIX for Dummies Questions & Answers

Shutting down the Server

Hi Is there anyway i can find out from which terminal a shutdown command has been run from ? :( (3 Replies)
Discussion started by: ktech
3 Replies

4. Ubuntu

Ubuntu Hangs when shutting down

i really dont know any other way to put it besides that Ubuntu 8.04, that i just installed on my computer hangs when it shuts down. the bar depletes the orange like it should, but it never actually shuts down. anyone know whats going on? (3 Replies)
Discussion started by: Texasone
3 Replies

5. Solaris

Zone stuck in shutting down state.

One of my zone got stuck while rebooting in shutting down state. I tried following 1. Halt the zone with zoneadm -z zone1 halt 2. kill zoneadmd process for that zone and halt the zone but none helped me. How can i shut it down and restart it ? ---------- Post updated 10-09-09 at 01:54 AM... (0 Replies)
Discussion started by: fugitive
0 Replies

6. UNIX for Dummies Questions & Answers

critical temperature eached, shutting down

Hey all, I have attached an image of a problem that I've been having since last night. My computer will be on no more than 5-10 min and I'll get this message that pops up and my computer shutsdown. I know for a fact my computer is not overheated becasue I will have it off for hours and then... (7 Replies)
Discussion started by: pullmand
7 Replies

7. Solaris

I Need to edit message at shutting down

on solaris 8 i edited file rc0 in /sbin at last line ex. /sbin/sync; /sbin/sync; /sbin/sync # Unmount file systems. /usr, /var, /var/adm, /var/run are not unmounted by # umountall because they are mounted by rcS (for single user mode) rather than # mountall. If this is changed,... (1 Reply)
Discussion started by: infjustice
1 Replies

8. AIX

Getting error while shutting down

Hi, I am getting the error "/etc/rc.shutdown failed. Shutdown aborting" while shutting down the os. Please suggest. (1 Reply)
Discussion started by: manoj.solaris
1 Replies

9. Fedora

Script for shutting down 48 computers

Hi All, I am pretty new to unix type languages. At work we have a server room with about 50 windows computers in one system and 50 in a unix system. We sometimes have power outages and I don't like the power slam. I wrote a windows batch file using sysinternals help to shutdown the windows... (4 Replies)
Discussion started by: Jeff Rollins
4 Replies

10. UNIX for Beginners Questions & Answers

DISKs are gone after shutting down and replace an FC card

Hi there, I had issue with one of MY FC cards on T4-2 servers so system team replace it and start the machine but when launch FORMAT command so I don't see my shared disks coming from storage controller. i have checked at the Fabric switch so WWN numbers are visible and zones are ok and after... (1 Reply)
Discussion started by: janakors
1 Replies
SHUTDOWN(8)						Linux System Administrator's Manual					       SHUTDOWN(8)

NAME
shutdown - bring the system down SYNOPSIS
/sbin/shutdown [-akrhPHfFnc] [-t sec] time [warning message] DESCRIPTION
shutdown brings the system down in a secure way. All logged-in users are notified that the system is going down, and login(1) is blocked. It is possible to shut the system down immediately or after a specified delay. All processes are first notified that the system is going down by the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, runlevel 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where administrative tasks can be performed; this is the default if neither the -h or -r flag is given to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for these runlevels in the file /etc/inittab. OPTIONS
-a Use /etc/shutdown.allow. -k Don't really shutdown; only send the warning messages to everybody. -r Reboot after shutdown. -h Halt or power off after shutdown. -P Halt action is to turn off the power. -H Modifier to the -h flag. Halt action is to halt or drop into boot monitor on systems that support it. Must be used with the -h flag. -f Skip fsck on reboot. -F Force fsck on reboot. -n [DEPRECATED] Don't call init(8) to do the shutdown but do it ourself. The use of this option is discouraged, and its results are not always what you'd expect. -c Cancel a waiting shutdown. ("shutdown now" is no longer waiting.) With this option it is of course not possible to give the time argument, but you can enter explanatory message arguments on the command line that will be sent to all users. -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. time When to shutdown. warning message Message to send to all users. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 dig- its) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait. The word now is an alias for +0. If shutdown is called with a delay, it will create the advisory file /etc/nologin which causes programs such as login(1) to not allow new user logins. This file is created five minutes before the shutdown sequence starts. Shutdown removes this file if it is stopped before it can signal init (i.e. it is cancelled or something goes wrong). It also removes it before calling init to change the runlevel. The -f flag means `reboot fast'. This only creates an advisory file /fastboot which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide not to run fsck(1) since the system has been shut down in the proper way. After that, the boot process should remove /fastboot. The -F flag means `force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a special `force' flag so that even properly unmounted file systems get checked. After that, the boot process should remove /forcefsck. The -n flag causes shutdown not to call init, but to kill all running processes itself. shutdown will then turn off quota, accounting, and swapping and unmount all file systems. ACCESS CONTROL
shutdown can be called from init(8) when the magic keys CTRL-ALT-DEL are pressed, by creating an appropriate entry in /etc/inittab. This means that everyone who has physical access to the console keyboard can shut the system down. To prevent this, shutdown can check to see if an authorized user is logged in on one of the virtual consoles. If shutdown is called with the -a argument (add this to the invocation of shutdown in /etc/inittab), it checks to see if the file /etc/shutdown.allow is present. It then compares the login names in that file with the list of people that are logged in on a virtual console (from /var/run/utmp). Only if one of those authorized users or root is logged in, it will proceed. Otherwise it will write the message shutdown: no authorized users logged in to the (physical) system console. The format of /etc/shutdown.allow is one user name per line. Empty lines and comment lines (prefixed by a #) are allowed. Currently there is a limit of 32 users in this file. Note that if /etc/shutdown.allow is not present, the -a argument is ignored. HALT OR POWEROFF
The -H option just sets the init environment variable INIT_HALT to HALT, and the -P option just sets that variable to POWEROFF. The shut- down script that calls halt(8) as the last thing in the shutdown sequence should check these environment variables and call halt(8) with the right options for these options to actually have any effect. Debian 3.1 (sarge) supports this. FILES
/fastboot /etc/inittab /etc/init.d/halt /etc/init.d/reboot /etc/shutdown.allow NOTES
A lot of users forget to give the time argument and are then puzzled by the error message shutdown produces. The time argument is manda- tory; in 90 percent of all cases this argument will be the word now. Init can only capture CTRL-ALT-DEL and start shutdown in console mode. If the system is running the X window System, the X server pro- cesses all key strokes. Some X11 environments make it possible to capture CTRL-ALT-DEL, but what exactly is done with that event depends on that environment. Shutdown wasn't designed to be run setuid. /etc/shutdown.allow is not used to find out who is executing shutdown, it ONLY checks who is currently logged in on (one of the) console(s). AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
fsck(8), init(8), halt(8), poweroff(8), reboot(8) November 12, 2003 SHUTDOWN(8)
All times are GMT -4. The time now is 10:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy