Re: extensible/mteTriggerTable solaris behaviour

2004-09-16 Thread Allan Mcintosh
I think I have found a *work around*, (work around != fix), for "montitor . extResult != 0" not working on solaris. In irc I was given the idea to try extResult.1 != 0 which means a monitor entry is required for each exec entry as shown below. exec tester1 /bin/sh /tmp/tester1 exec tester

FW: extensible/mteTriggerTable solaris behaviour

2004-09-16 Thread Bruce Shaw
Title: FW: extensible/mteTriggerTable solaris behaviour *copied to coders* I tried using: exec tester1 /bin/sh /tmp/tester1 exec tester2 /bin/sh  /tmp/tester2 exec tester3  /bin/sh /tmp/tester3 exec tester4  /bin/sh /tmp/tester4 exec tester5  /bin/sh /tmp/tester5 monitor -r 30 -o

Re: extensible/mteTriggerTable solaris behaviour

2004-09-15 Thread Allan McIntosh
I tried using: exec tester1 /bin/sh /tmp/tester1 exec tester2 /bin/sh /tmp/tester2 exec tester3 /bin/sh /tmp/tester3 exec tester4 /bin/sh /tmp/tester4 exec tester5 /bin/sh /tmp/tester5 monitor -r 30 -o extNames.1 -o extOutput.1 "tester1 status" extResult.1 != 0 monitor -r 30 -o extNames.2 -o e

RE: extensible/mteTriggerTable solaris behaviour

2004-09-15 Thread Bruce Shaw
Title: RE: extensible/mteTriggerTable solaris behaviour Did some more testing, documented here http://sourceforge.net/tracker/index.php?func=detail&aid=1028105&group_id=12694&atid=112694 Briefly, the sleeps have nothing to do with it.  It only takes two entries to make it f

Re: extensible/mteTriggerTable solaris behaviour

2004-09-14 Thread Allan Mcintosh
http://sourceforge.net/tracker/index.php?func=detail&aid=1028105&group_id=12694&atid=112694 -- Allan McIntosh Software Designer Atreus Systems, Inc. 613-233-1741 ext: 217 (Office) 613-233-8204 (Fax) [EMAIL PROTECTED] www.atreus-systems.com

extensible/mteTriggerTable solaris behaviour

2004-09-14 Thread Allan Mcintosh
Start snmpd solaris9 (uname -m: sun4u) with 5 exec scripts a few with `sleep 6` in them, each returns 0. I can produce the following over and over again.. In mte_run_trigger() just after the call to snmp_add_null_var() next_oid is 1 extResponse.1, extOutput.1 is successfully retrieved.