This is rather lame, but none the less a bug. If I use a hostname in hosts.cfg that is a CNAME record that doesn't point to a A record, xymonnet crashes. The strace of the event:
recvfrom(4, "9g\205\200\0\1\0\1\0\0\0\0\vlame_name\4orix\3co"..., 4097, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("1.1.1.1")}, [16]) = 74 --- SIGSEGV (Segmentation fault) @ 0 (0) --- rt_sigaction(SIGSEGV, {SIG_DFL, [SEGV], SA_RESTORER|SA_RESTART, 0x7fae2a535910}, {0x4279f0, [], SA_RESTORER, 0x7fae2a535910}, 8) = 0 clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fae2b6dd9d0) = 26817 chdir("/usr/local/xymon/server/tmp") = 0 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 tgkill(26449, 26449, SIGABRT) = 0 --- SIGABRT (Aborted) @ 0 (0) --- +++ killed by SIGABRT (core dumped) +++
Of course if there is no DNS entry at all, it complains and just uses the IP address included in the hosts.cfg file, but for a 'dangling' CNAME it crashes. This happens in both 4.3.27 and 4.3.28.
thanks, Phil