Comma-delimited also works for some people, but that depends on your
"mail" program. Why? Because a definition like this
$ALERTGROUP=user-490a14721d84@xymon.invalid,user-0ea294303ceb@xymon.invalid,user-85a97e0c328b@xymon.invalid
ends up being passed as a command-line parameter to the $MAIL
program. So if your mail-program understands a list of recipients
separated by commas, it is actually more efficient because Hobbit only
needs to run the mail program once with the comma-separated list of
recipients.
Does hobbit understand that the comma delimited are actually individual
email addresses for the purpose of deciding who to page? ie, say you had
another rule which said don't page user-0ea294303ceb@xymon.invalid, would it know to
remove user-0ea294303ceb@xymon.invalid from the rule?
I'm assuming it doesn't, as otherwise, I assume it would know they are
individual addresses and pass them individually to mail....
Regards,
Adam
--
--
Adam Goryachev
Website Managers
Ph: +XX X XXXX XXXX user-eaec2ffb4cbc@xymon.invalid
Fax: +XX X XXXX XXXX www.websitemanagers.com.au