09-09-2017
I would advise againt using init 0 on physical hardware before your have stopped all your LDOM(s) via ldm stop or init 0 (or 5) inside the LDOM.
This goes against documented practice for Oracle VM server.
If you issue ldm stop <domain>, it will send a shutdown signal to LDOM (in you case also a global zone), global zone / ldom sends a shutdown signal to zones.
It will stop all the services and daemons properly and umount the filesystems.
A clean shutdown of LDOM and zones inside will be made.
Question is why would you want to issue init 0 or init 5 on hypervisor, before stopping the domains ?
Hope the helps
Regards
Peasant
These 2 Users Gave Thanks to Peasant For This Post:
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
When the solaris 8 have come up, which command can find out the current run-level?
thanks. (2 Replies)
Discussion started by: nianzhe
2 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I need a help. I need to know:
1. the individual core id, physical id of a running process on multicore inside a program. The system file /proc/cpuinfo shows all the ids of all the processes. But I need to know runtime, what exact core id and physical id , the running process has.... (0 Replies)
Discussion started by: debrajde
0 Replies
3. Windows & DOS: Issues & Discussions
hi all
in our office we have windows 2003 server for one particular application designed by our team need one service must be running on windows server now when we run process from any user it runs till that user is logged in as soon as he logs off service stops running.
we had win 2000... (1 Reply)
Discussion started by: zedex
1 Replies
4. Solaris
Dear Friends..!!
i am quit confused about the SOLARIES RUN level that is 0 . 1 or s S ...
please let me know the diffirence between these run level ... 0,1 and s S...
have a great day
Uday naikwadi (1 Reply)
Discussion started by: udayn
1 Replies
5. SuSE
Hello,
I recently updated a test system from Suse 8 to 9.3. Now our runlevel services program doesn't work, but works fine on our other 9.3 boxes.
We have a file in /etc/init.d/rc3.d called S99fooprog(not actual name ofcourse).
It just has a command to start a program daemon up. Anyways... (3 Replies)
Discussion started by: benefactr
3 Replies
6. Solaris
Hi Experts,
A stupid question for experts :confused: !!
What is the difference between run level ‘1', runlevel ‘S' and small ‘s'.
As per my understanding the difference between S and 1 is that in case of ‘S' it only going to mount the critical file system which ideal should be... (2 Replies)
Discussion started by: kumarmani
2 Replies
7. Solaris
Hi All,
In Solaris 9 and below
I will get the init run-level by checking the /etc/inittab entry
is:3:initdefault:
But in Solaris 10 we are using the smf functionality.
Here how I can get the init default run level.
Please help me in this problem.
Regards,
... (2 Replies)
Discussion started by: kalpeer
2 Replies
8. Solaris
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
9. UNIX for Dummies Questions & Answers
A Bourne Shell script is placed in /etc/rc.d/rc3.d called S57apache. What will happen with this script when the run level is changed from 5 to 3?
many thanks (4 Replies)
Discussion started by: lemon_06
4 Replies
10. Shell Programming and Scripting
Is there a way to tell what runlevel is currently being used,
for example is a user is using the gui
or is the have pressed Alt+Ctrl+F1 to drop to the terminal?? (3 Replies)
Discussion started by: ab52
3 Replies
LEARN ABOUT CENTOS
stopping
stopping(7) Miscellaneous Information Manual stopping(7)
NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO
starting(7) started(7) stopped(7) init(5)
Upstart 2009-07-09 stopping(7)