Xymon Mailing List Archive search

XYMONNETWORK environment variable

list Paul Root
Thu, 5 Jan 2012 15:43:07 -0600
Message-Id: <user-62aa806782e5@xymon.invalid>

Thanks!

Paul Root    - Engineer III
Managed Services Systems - CenturyLink

-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On
Behalf Of Henrik Størner
Sent: Thursday, January 05, 2012 2:52 PM
To: xymon at xymon.com
Subject: Re: [Xymon] XYMONNETWORK environment variable

On 05-01-2012 21:46, Root, Paul wrote:
So a follow up.

I'm guessing I need a new section for an additional xymonnet?
Yes.
[xymonnet]
ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
NEEDS xymond
CMD xymonnet --report --ping --checkresponse
LOGFILE $XYMONSERVERLOGS/xymon-network.log
INTERVAL 5m

[xymonnet2]
ENVFILE /usr/lib64/xymon/server/etc/xymonserver.cfg
NEEDS xymond
CMD XYMONNETWORK=IAD xymonnet --report --ping --checkresponse
LOGFILE $XYMONSERVERLOGS/xymon-network.log
INTERVAL 5m

Is that right? And it's ok to use the same log file?
Not quite right, because the CMD setting doesn't permit you to set
environment variables that way (the command isn't passed to a shell,
but
executed directly). So the easiest thing to do is to have a shell-
script
"wrapper" around the xymonnet command, that sets the XYMONNET
environment variable.
Should I have another xymonnetagain then too?
Good question - off the top of my head, I'd say "yes, you should".


Regards,
Henrik
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.