Happy New Year Everyone.
Looking for a little insider help -
First thing, I'm creating a custom command line probe. Let me first say that
this is an excellent tool that I seemingly can do anything with. It does have
some quirks that I think I need some clarification on.
My goal is to get status on some processes I have running. I query my
processes, and it returns the status through the standard stdout:
\{ $blah1 := "Status message", $blah2 := "Status message2" }
I see two interesting behaviors when I run this. First, it seems that there is
a limit on the size of the variable that can be set in the stdout response. If
it gets too large, the probe stops updating. I assume that there is a size
limit to any probe variable.
Second thing is that the status window underlines the returned values from the
command line probe. Similar to what you would see if something is a value that
could be graphed. In fact, when I click on it, it tries to create a graph.
With a textual string response, obviously this doesn't work. Is there any way
to instruct IM not to consider the returned variable as eligible for graphing?
Lastly - I've put some effort into trying to take advantage of the redundant
polling feature. According to the docs, the attributes to the device must match
for it to be considered the same. I wrote some perl to parse the output of
remoteaccess scripting and compare the fields of every device. It seems that as
long as the hash variable of ProbeXML field matches, it is considered the same
device. Can someone at Dartware confirm that?
I know this jumps around a little, bit I thought sending one email might be
easier. Appreciate the help,
Tony
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
