Re: bin/58558: syslog.conf(5) man page example does not work.

[xover2391%hush.com@localhost]

Of the ten devices I configured for testing, I can confirm that all seven of the routers have their respective IP address in the fourth field of any syslog message saved by the NetBSD server.

I can confirm that the Synology unit (which has its System Name set to "nas") has "nas" in the fourth field of any syslog message saved by the NetBSD server instead of its IP address, regardless of whether the Synology was sending the syslog messages in BSD form or IETF form. All I had to do was to alter the block specifier to "+nas" in /etc/syslog.conf, and the Synology's syslog messages were then being written to the file I specified.

I can confirm that the other network switch (not a HP unit like the first one is) has the three character month abbreviation of its local time in the fourth field, just as the HP network switch has. I am surprised to see the same behaviour from two different network switch manufacturers. By changing the block specifier to "+<Month>", the syslog messages from either network switch could be saved to a separate file from the other messages, but not separate from each other. Not a good workaround, for so many reasons.

In any case, it seems as if the original reason for opening this bug report has been solved. For the example I listed in the syslog.conf(5) man page to work correctly, the NetBSD server needs to have a hostname set (I eventually did that in /etc/rc.conf) and with the use of the "+@", "-@", and "+<IP address>" or "+<hostname>" or "+<whatever is in the fourth field of a syslog message from a remote device>" block specifiers, syslog messages from different devices can be saved to different files.

This bug report can be closed. Thanks to all who assisted.