Yes this is normal.
actionsvr (prime, if you will, the one started by ovstart) manages a queue of
actions and spawns children of the same name to execute them. This allows
actions to keep up with events. It is normal to have two in steady state (no
actions being performed) and the number rises to accommodate as many as there
are outstanding actions to be performed. So on occasion you will see more,
though the number should drop back to two as the outstanding actions complete.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Geoffrey Cheng <gcheng@CA.IBM.COM> on 07/28/99 12:14:57 PM
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: multiple actionsvr daemons running
Hi,
I am on NetView 5.1.1 and recently enable about 10 complicated rules in
background.
Thereafter, I found that there are two actionsvr daemon running, one
spawned by
ovspmd and the other spawned by the first one, based on the output of
nvstat.
But the rules are working fine as well as other functions regarding event
correlation.
My question is, is it normal to have multiple actionsvr daemons running and
sharing
one nvcorrd?
Thanks.
Best Regards
Geoffrey Cheng
e-mail: gcheng@ca.ibm.com
|