remote syslog

dan info at hostinthebox.net
Thu May 26 18:07:48 UTC 2005


Tim Holmes wrote:
> Hello All:
> 
> I am trying to use one of my linux boxes to get information from my
> foundry switches (and eventually a lot of other gear) using the syslog
> facility.  This will be in addition to SNMP which I am already using via
> CACTI
> 
> I have managed to configure things so that the messages are heading to
> /var/logs/messages, but I cannot seem to get them to go to the device
> specific files that I have designated.
> 
> Here is a copy of my /etc/syslog.conf file
> 
> # Log all kernel messages to the console.
> # Logging much else clutters up the screen.
> #kern.*                                                 /dev/console
> 
> # Log anything (except mail) of level info or higher.
> # Don't log private authentication messages!
> *.info;mail.none;authpriv.none;cron.none
> /var/log/messages
> 
> # The authpriv file has restricted access.
> authpriv.*                                              /var/log/secure
> 
> # Log all the mail messages in one place.
> mail.*                                                  /var/log/maillog
> 
> 
> # Log cron stuff
> cron.*                                                  /var/log/cron
> 
> # Everybody gets emergency messages
> *.emerg                                                 *
> 
> # Save news errors of level crit and higher in a special file.
> uucp,news.crit                                          /var/log/spooler
> 
> # Save boot messages also to boot.log
> local7.*
> /var/log/boot.log
> 
> #send messages from Lancelot to Lancelot.log
> 192.168.0.225.*
> /var/log/lancelot.log
> 
> 
> #send messages from tristan. tristan.log
> 192.168.0.231.*
> /var/log/tristan.log
> tristan.*
> /var/log/tristan.log
> 

Tim -

Per 'man syslogd':

To enable this [network logging on the server] you have to specify the 
-r option on the command line.  The default behavior is that syslogd 
won’t listen to the network.

If you start syslogd in this manner on your central logging server, and 
ensure that port 514/udp is acecssable on the server by the clients, 
this will work.

Hope that helps
-dant




More information about the users mailing list