10-10-2007
Thanks for the reply.
Unfortunately I cannot stop the services on this server as it's being used.
My next question, does the MKSYSB still 'work', even though it's told me it failed at 79%?
10 More Discussions You Might Find Interesting
1. AIX
Hi, I'a a new member here.
My company just bought p570 with 8 LPAR (previously we have p650 with 4 LPAR).
Did anyone have procedure how to setup NIM server (NIM LPAR) and how to install other new LPAR to use the NIM server (as client).
Appreciate your help and thank you very much.
Rgds,
David (0 Replies)
Discussion started by: dshg
0 Replies
2. AIX
Is anybody using a NIM server for DR recovery purposes? If so, how are you handling Volume Groups outside of root? (0 Replies)
Discussion started by: kd30185
0 Replies
3. AIX
Hi Guys..
Got a NIM issue.. Am trying to pull a image of a client from NIM server.
am getting the following error... in standard error output..
0042-001 nim: processing error encountered on "master":
Usage: rm File...
Am using the same script to pull image and it works fine..... (1 Reply)
Discussion started by: balaji_prk
1 Replies
4. AIX
I try to migrate a NIM server from one server to another.
I try to do a mksysb on NIM server
restore the NIM server's mksysb to a client through NIM installation
shutdown NIM server
start newly installed client as NIM server
Does anyone do this before? who can give me some suggestion? (1 Reply)
Discussion started by: yanzhang
1 Replies
5. AIX
Hello All,
I believe my NIM master is fine. lsnim and cat /etc/niminfo gives me the right output. While doing "lsnim" on a client machine, I get ksh:lsnim:"not found".
Please someone be nice enough to explain what are the steps to verify the master and client connectivity to do all the NIM... (3 Replies)
Discussion started by: solaix14
3 Replies
6. AIX
Can any one help.....
How will do migration through NIM server? (4 Replies)
Discussion started by: AIXlearner
4 Replies
7. AIX
I have never used NIM. Please help with the steps for configuring NIM server and client.
thanks
Pchangba (3 Replies)
Discussion started by: pchangba
3 Replies
8. AIX
hello folks,
Can someone help me troubleshoot the NIM Server
NIM MASTER: >>
# hostname
oldbcoedv
# cat /etc/hostname
192.52.100.29 bcoeqa bcoeqa.bin.com.sa
192.52.100.66 oldbcoedv
# cat /etc/bootptab
.....
# T180 -- (xstation only) -- enable virtual screen
#NO CLIENTS... (6 Replies)
Discussion started by: filosophizer
6 Replies
9. AIX
Hi.
I would like to try installation via NIM server. I have set up :
lsnim
master machines master
boot resources boot
nim_script resources nim_script
NET_EN0 networks ent
mksysb_AIX_6141 resources ... (4 Replies)
Discussion started by: phobus
4 Replies
10. AIX
I have configured the NIM Master using AIX 5.3.7, I am getting below message bootp:bootp request fail:0 while booting nim client.
Though both system are able to ping each other.
Regards
Manoj (5 Replies)
Discussion started by: manoj.solaris
5 Replies
LEARN ABOUT HPUX
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)