The options when the syslogd daemon are started will need to be changed from the default options.
By default, the syslogd daemon on Linux, FreeBSD, and most other versions of Unix accepts syslog packets only from the local host. In fact, the way Linux/FreeBSD/etc. force this behavior is the sylogd daemon doesn't open an IP socket on port 514 to even receive syslog messages from the network. A Unix domain socket is used by a local application to communicate with the local syslogd server instead (a named socket has nothing to do with the Internet protocol and doesn't normally go over a network).
You should look in the man page for syslogd on the version of Linux you plan to use. On Red Hat, Centos, Fedora, etc., I believe -r will enable remote logging. It also usually makes sense to use the -x option, which disables reverse DNS lookups for any remote packets received. Otherwise the syslogd server will request a DNS lookup for any remote log packets received to convert the source IP address to a name. This can often be costly. So instead of the remote machine name, the IP address is printed by syslog in the log files. On Red Hat, Centos, Fedora, etc., the options that syslogd starts with can be set in the /etc/sysconfig/syslog text file by changing the default SYSLOGD_OPTIONS="-m 0" to SYSLOGD_OPTIONS="-r -x m 0"
Again, use man pages for syslogd on the linux distro to determine the appropriate switches and how to change the options used to start syslogd.
-msbaker
|