[Novalug] SysLogging should be easy right?
jwtuttle at gmail.com
Fri Mar 23 14:04:19 EDT 2012
I went through the same process just the other week to capture log
information from a router, although it was on an Ubuntu box rather than
Although you can do this with plain-old syslog, I decided on syslog-ng,
which is a quite a bit more flexible. (You can log to a database,
trigger scripts when certain events are logged, etc.) It may or may not
be overkill for your needs, but there are a lot of good HOWTOs around if
you want to go that route.
FAQ (has links to commented config files):
Centralized Logging with Periodic Reporting HOWTO:
If that's too much and you want to stay with the stock syslog, I found
this guide to be pretty helpful in the past (has instructions both for
Debian and RH based distros):
On Fri, 2012-03-23 at 12:25 -0400, daniel wrote:
> The concept is pretty straight forward. You set up the process and
> the firewalls (if any) and the next thing you know, there are logs
> coming in from external devices to the server you set up right?
> Well, obviously not easy. Worse, I'm not finding any useful howto
> guides. Anyone know of any?
> Platform is CentOS 6.x. All I want to do is catch incoming log
> messages from a device on the network 192.168.26.10. Not totally
> concerned about security though a little of that would be nice. The
> device doesn't know how to do encryption though.
> Anyone know of a good how-to or could offer one?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://calypso.tux.org/pipermail/novalug/attachments/20120323/57ada8d1/attachment.bin
More information about the Novalug