syslogd support
There are a number of blogs and such explaining how to enable syslogd under Mac OS X to accept syslog messsages sent from remote devices. Some of the older information presented indicates this technology came from FreeBSD:
http://hints.macworld.com/article.php?story=20040301223642276
http://macosx.com/forums/howto-faqs/47791-howto-syslog-remote-events-etc.html
I understand the need to modify /System/Library/LaunchDaemons/com.apple.syslogd.plist and how, e.g...
http://meinit.nl/enable-apple-mac-os-x-machine-syslog-server
...so let's take that as a given.
My questions are as follows:
1) Did syslogd/syslog.conf under Mac OS X ever actually support the program/hostname block concept mentioned in the first couple of links (particularly the first one)? These features aren't documented as far as Apple is concerned, but that doesn't necessarily mean they don't work, esp. if the Apple code was really derived from FreeBSD.
2) If syslog.conf program/hostname blocks ever worked, was there an OS X release with which they stopped working, and if so, what was that release?
3) Assuming a hostname block is available, from the (FreeBSD) documentation available, it appears one could specify the following at the beginning of syslog.conf:
#+ipaddr1
*.* /var/log/remote/remsys1.log
#+*
#+ipaddr2
*.* /var/log/remote/remsys2.log
#+*
#...rest of supplied syslog.conf...
Conceptually, the desired behavior is to log all messages from ipaddr1 and ipaddr2 exclusively to /var/log/remote/remsys1.log and /var/log/remote/remsys2.log, respectively. Is this the correct syntax and will it result in the desired behavior?
I've seen references that a ported syslog-ng would provide for this functionality, but if I happen to have access to a system where it's available natively, that would be preferred.
Thanks,
Mike