UPDATE: The problem seems to be on the client side, because when I do this: logger -p local5.info test the file does show up properly on the syslog-ng host. Anyone have an idea why the other processes that write to local5 on the client are not logging to the remote host? > local5.* /var/log/mylogfile.log _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: Forward local5.* to remote syslog-ng server
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "CentOS mailing list" <centos@xxxxxxxxxx>
- Subject: Re: Forward local5.* to remote syslog-ng server
- From: "Sean Carolan" <scarolan@xxxxxxxxx>
- Date: Fri, 14 Mar 2008 13:04:48 -0500
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <277020fc0803141035scc037aeo222f5710baa5f764@xxxxxxxxxxxxxx>
- References: <277020fc0803141035scc037aeo222f5710baa5f764@xxxxxxxxxxxxxx>
- Follow-Ups:
- Re: Forward local5.* to remote syslog-ng server
- From: Sean Carolan
- Re: Forward local5.* to remote syslog-ng server
- References:
- Forward local5.* to remote syslog-ng server
- From: Sean Carolan
- Forward local5.* to remote syslog-ng server
- Prev by Date: RE: Recommendations for a "real RAID" 1 card on Centos box
- Next by Date: Re: Recommendations for a �card on Centos box
- Previous by thread: Forward local5.* to remote syslog-ng server
- Next by thread: Re: Forward local5.* to remote syslog-ng server
- Index(es):
 |