RE: DM Numeric custom script monitor

The script must *exit* with a return code of 0 or the monitor

will fail, true.  However, the value you are comparing against

is not the return code, but rather a numeric value that is echoed

to standard output.

 

For example:

#!/bin/sh

[…]

echo “5”

exit 0

 

The exit value tells DM whether or not the monitor ran correctly.

The stdout value is what you are monitoring for.

 

Loren Cain

Digicon Corp.

 

 

---

From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx [mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx] On Behalf Of Brian Kraftchick
Sent: Wednesday, April 28, 2004 4:08 PM
To: Tme10 (E-mail)
Subject: [*Possible SPAM*] [tme10] DM Numeric custom script monitor

 

FW 3.7.1 on Win2K

 

I have a question that I'm assuming is only a question to me because I don't quite understand something, so hopefully any answers will clear this up.  What is the purpose of a numeric custom script monitor's response level parameters being selectable (meaning you can enter any numbered value as the threshold), if any script that is run and returns anything other than a 0 produces an E.Exec and ultimately a monitor failure.  In other words....when setting up the monitor and editing the response levels, why even be allowed to key in different numbers when it appears that numeric custom script monitors only work completely when the script exits with a 0...exiting with anything else causes the E.Exec response.

 

Thanks in advance for any insight !

 

Brian Kraftchick

Network Administrator

Old Dominion Freight Line

Ph: (336) 822-5938

Fax: (336) 822-5149

E-mail: brian.kraftchick-MRmd0vlZXUo@xxxxxxxxxxxxxxxx

Web Site: www.odfl.com