Remote syslog is cool but how it is not going to be of any use to me if i cannot segregate my logs per client out of the box.

I would like to have “server_1” logs to go to “/var/log/servers/server_1.log” on the remote machine and so on…

Right now this thing just dump every server logs into one file /var/log/messages.

Apparently this is possible only in UNIX not in LINUX, so this is not going to work on my RedHat’ ish BOX.

+server_1.ycsoftware.net
*.* /var/log/servers/server_1.log
NOT WORKING ON LINUX

Note that i am talking about the standard syslogd server. There is another syslog server called syslog-ng, I will try that one and see if it can be useful. In the meantime, if anybody managed to segregate the standard linux syslog per remote client please let us know. Everybody could benefit from it.

1. First Make sure that there are no firewalls blocking the connection from the syslog server to the syslog client
2. Make sure that the computers are on the same network
3. Make sure that the syslog daemon is using the right config file for the syslog clients.
Some systems use syslog.conf others use rsyslog.conf. Also some system have both config files and syslogd only uses one of them. Trust me I found that out the hard way.

4. Make sure that you restart the syslog servers after making changes to the config files

Reference
http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch05_:_Troubleshooting_Linux_with_syslog

http://www.aboutdebian.com/syslog.htm

http://publib.boulder.ibm.com/infocenter/tpfhelp/current/index.jsp?topic=%2Fcom.ibm.ztpf-ztpfdf.doc_put.cur%2Fgtpc1%2Fconstmt.html