It is certainly possible . .
That is what is noted in the man-page, but I have a memory of digging through the code and noticing that a semicolon was accepted in the same way as the comma. Of course, that was years ago and I can not now find my notes on the subject.
FWIW, these semicolons parse correctly on a host's 'info' page
But I suppose that doesn't mean they are parsed correctly everywhere downtime is considered.
And the total number of complaints in the log doesn't align with the number of downtimes I have defined with semicolons. Maybe those messages are being triggered by messages for hosts with downtimes defined . . but my downtimes are (for the most part) defined in .default. lines so affect every host (so every message evaluation).
If the semicolon is causing a parsing problem, I'd expect to see one for each line in hosts.cfg
If it is causing a problem evaluating messages, I'd expect to see one for each yellow or red bubble
I'm not saying it /isn't/ causing those problems. Just that I can't make the number of logged lines reconcile with either scenario.
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
On 11/27/2023 10:38 AM, Jeremy Laidman wrote:
Hi John
On Tue, 28 Nov 2023, 06:24 John Thurston, <user-ce4d79d99bab@xymon.invalid> wrote:
I have 'DOWNTIME' specifications like
DOWNTIME=60:*:*;*:1630:0800
Is it possible the semicolon is supposed to be a comma?
J