Re^2: Process Monitoring Madness

Replies are listed 'Best First'.
Re^3: Process Monitoring Madness by Corion (Patriarch) on Oct 08, 2018 at 12:47 UTC
Can you show us input that should/shouldn't match? Ideally for debugging, you hardcode that input, so we can test it without running `crontab -l` or the service status commands... Personally, I've grown fond of Regexp::Debugger, which makes it very convenient to see where a regular expression deviates from the intended path...	[reply] [d/l]
Re^4: Process Monitoring Madness by woland (Novice) on Oct 08, 2018 at 12:59 UTC
Hi Corion I have updated the OP with examples Thanks	[reply]
Re^5: Process Monitoring Madness by Corion (Patriarch) on Oct 08, 2018 at 13:11 UTC
Thanks! I had originally misread/misunderstood your code as I thought it also read the output of the `/etc/init.d/*` scripts, but it doesn't, so the output of them doesn't really matter.	[reply] [d/l]
Re^6: Process Monitoring Madness by Corion (Patriarch) on Oct 08, 2018 at 13:31 UTC
Re^7: Process Monitoring Madness by woland (Novice) on Oct 08, 2018 at 13:49 UTC
Re^4: Process Monitoring Madness by woland (Novice) on Oct 08, 2018 at 12:53 UTC
Hi Corion The below is triggering alerts today even though date +%w == 1 `00 05 * * 0 /etc/init.d/smart_tse-ah2 start 00 22 * * 0 /etc/init.d/smart_tse-ah2 stop` [download] The regex itself appears fine as these false alerts are sporadic and the below crontab have so far caused no alerts today `00 05 * * 1-5 /etc/init.d/tsefull start 00 22 * * 1-5 /etc/init.d/tsefull stop` [download] Thanks	[reply] [d/l] [select]
Re^3: Process Monitoring Madness by poj (Abbot) on Oct 08, 2018 at 17:46 UTC
Where in the program is `%schedule` declared ? poj	[reply] [d/l]