Rulesets in ESE.automation are loaded by actionsvr, not by ovactiond.
ovactiond has nothing to do with rulesets; he's the guy who executes
automatic actions from defined in Event Configuration (trapd.conf).
To get your rulesets reloaded after you put them in ESE.automation, do
ovstop actionsvr and then ovstart actionsvr when that completes. You
should be able to see that your rulesets have been loaded or re-loaded by
browsing /usr/OV/log/nvaction.alog
James Shanks
Tivoli (NetView for UNIX) L3 Support
Greg Redder <redder@yuma.ACNS.ColoState.EDU> on 07/24/98 05:58:52 PM
Please respond to "REDDER Gregory J." <redder@yuma.ACNS.ColoState.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks)
Subject: ESE.automation
Dear all,
I am running NV5 on AIX4.2.1.
I make a modification to one of the rulesets that is loaded via
ESE.automation. However, I can't seem to make NetView reread that ruleset
without going through smit and stopping/restarting all daemons. I've tried
just stopping and restarting ovactiond, but that doesn't seem to force a
reload of the rulesets. I've tried doing a kill -1 on actionsvr and
nvcorrd (I know you aren't supposed to do it that way, but....) and that
doesn't work either. What is the easiest way to force a reread of the
rulesets loaded by ESE.automation?
Thank you --Greg Redder
Network Analyst
Colorado State University
==========================================================================
====
Greg Redder Academic Computing & Networking
Services
Colorado State University, ACNS Phone:(970)491-7222 FAX:
(970)491-1958
601 S. Howes, Room 625 E-mail: redder@yuma.colostate.edu
Fort Collins, CO 80523 PGP
Fprint:68CEE78C86AC452881B27249785FEE91
==========================================================================
====
|