nvcorrd does not expect to have any in-line actions which involve processes
that themselves spawn new shells or child processes. But if you think you
have discovered a bug and you want it fixed, then you will have to open a
call to Support and report it. Be prepared to trace the execution of your
failing ruleset and to ftp that along with the ruleset to the Level 2 group
for analysis. If they can see the bug in what you send or reproduce it
themselves, then they will open an APAR to get it fixed. They will be
happy to explain how to gather the data they need.
Tivoli (NetView for UNIX) L3 Support
Jose Luis Arbona Orovay <jarbo AT INFOCENTRE.GVA DOT ES> on 08/06/98 08:28:59 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView et alia <NV-L AT UCSBVM.UCSB DOT EDU>
To: NV-L AT UCSBVM.UCSB DOT EDU
cc: (bcc: James Shanks)
Subject: Re: Rulesets
Douglas Staub escribis:
> My first question is what type of handlers or decisions are you using
> within your ruleset? How often is the event occuring? James Shanks of
> Tivoli just sent a good piece on creating rulesets earlier this week and
> might be worth taking a look at.
Yes, I've read it.
> I have had similar problems using the inline action (hundreds of
> defuncts!), however, I soon learned from James that executing a script
> within an inline script is not a good idea if you are expecting many
> to be fully processed or if the script takes longer than 10 seconds or
> - this resulted in a modification to evaluate the event o my part using
> command for automatic action within the event itself and my problem has
> since disappeared.
May be this, I had 2 or 3 inline actions in my ruleset, and I have changed
them for Actions. By now no more defuncts appeared.
However, that's no the solution, an inline action shouldn't have this
problem, or almost, have a patch which resolved it.
Thanks. (and sorry for my english)