Configure ovactiond to use -w 0 (wait time of 0) and he should fork all your
processes to run in parallel rather than wait for each to complete. See the man
page. And use SMIT of the Frameowrk to configure the daemons and see if that
helps.
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
echevarria@es.ibm.com on 05/11/2000 06:27:22 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: nv-l@tkg.com
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] delay in automatic actions
Hi all,
I have a Netview 5.1.1 running on AIX 4.2.1. From it I manage
different networks and I want to have a monthly log on availability of some
network nodes. So I defined in trapd.conf some traps for specific nodes:
Node down, Node Up, Node Marginal, Interface down and Interface Up. These
traps are defined as the standard ones but affect only to the nodes I'm
interested in and they have the following "Command for Automatic Action":
print "'date + %h/%d/%Y, +%H:%M:%S', $2,$3" >> availability.log
It runs fairly well and generates a log with the interesting traps
only for the nodes I want. But, when I compare the date and time in my
availability.log with the date and time of the same event in trapd.log I
find that there are differences of 0 to 10 minutes between event in
trapd.log and in availability.log so I'm getting wrong information.
My questions are:
* Has ovactiond daemon any kind of buffer or queue where it keeps the
actions till buffer is full and then it launches them?
* Has anybody any proposal? (I don't want to use trapd.log)
Many thanks and regards,
Juan.
Juan Echevarr
ía López
AT&T Global Network Services
Internet: jechevarria@att.com
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|