<div>Almost all of our servers have the noconn defined but we want ssh , in each ext script ( also ran via CRONDATE) I test for the status of ssh if it's green I run the ext test. This was set because the ext scripts are ssh based and were hanging. </div>
<div>I also noticed the same thing you did in the man pages. I just wasn't sure if copying the entire xymonnet , having two duplicate stanzas was supported. </div>
<br><br><div class="gmail_quote"><p>On Wed, Aug 12, 2015 at 1:15 PM, J.C. Cleaver <span dir="ltr"><<a href="mailto:firstname.lastname@example.org" target="_blank">email@example.com</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>On Wed, August 12, 2015 10:42 am, Ricardo L. wrote:
<br>> I have xymonnet set to run weekly via crondate.
<br>> Now I have the need to monitor a single host ping and ssh every 5 minutes.
<br>> How would I go about doing this ?
<br><br>That's an interesting config.
<br><br>If you're okay with running all of the tests for that host (not just ping
<br>and SSH), then the easiest method would be to set up another invocation of
<br>xymonnet (in tasks.cfg) using the normal "INTERVAL" directive. Keep the
<br>options the same, but simply specify the particular host you're interested
<br>in at the end of the command line.
<br><br>Per https://xymon.com/help/manpages/man1/xymonnet.1.html, xymonnet will
<br>restrict itself to that/those if hostnames are given.
<br><br>It's not an especially efficient way to run xymonnet, but for most sized
<br>configs and on normal hardware that shouldn't be an issue.
<br><br><br>Might I ask, any particular reason for the 1 week, fixed-time run cycle?