Hmmm. A signal 9 is just that. You can find out the meaning of any signal by
doing "man signal". They are non-standard exits from UNIX. Signal 9 is the
process being killed by the operating system or another process for some reason.
Is that the only info you get from doing ovstatus?
If so, I'd call Support and open a problem so someone can help figure this out.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Geoffrey Cheng <gcheng@CA.IBM.COM> on 07/09/99 11:07:49 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: nvcorrd exit on signal No. 9
Hi,
I've met a problem with nvcorrd, when doing a ovstart, nvcorrd started for
a few seconds and then
died silently, on signal no. 9. I've commented out all the rules in
ESE.automation, but the problem still
exists. There is nothing shown up in nv6000.log file and nettl trace file.
Nobody is using the 1666 port
either.
Has anyone met the similar problem? meanwhile, the only sympton I can see
is the "exit on
signal no.9. And I notice from time to time that some daemons do exit on
certain numbers, where
I could find the definition of these exit code? There seems not in the
diagnostics guide or
programmer's references.
Thanks.
Best Regards
Geoffrey Cheng
|