For those interested, there is a great article written on creating a
syslog server locate at
http://www.foogazi.com/2006/09/07/se...syslog-server/

Cheers!

Adam K. wrote:
> For those interested, there is a great article written on creating a
> syslog server locate at
> http://www.foogazi.com/2006/09/07/se...syslog-server/
>
> Cheers!

Hrmm. . . This can pretty much be summarized in two sentences.

1. Run syslogd with the -r option ( "flag" ) on the server.
2. Modify syslogd.conf on "clients" machines to log output to the IP of
the server.

Voila!

On Tue, 31 Oct 2006, Mike wrote:
> Adam K. wrote:
>> For those interested, there is a great article written on creating a
>> syslog server locate at
>> http://www.foogazi.com/2006/09/07/se...syslog-server/
>
> Hrmm. . . This can pretty much be summarized in two sentences.
> 1. Run syslogd with the -r option ( "flag" ) on the server.
> 2. Modify syslogd.conf on "clients" machines to log output to the IP of
> the server.

ya might also want to muck the log server's /etc/hosts file so
as to add entries for whatever clients you expect to be logging.
(thus avoiding dns lookups to find the clients name, minimizing
load on host and net).

and if the box is on an insecure net, ya might want to cobble up
some iptables rules limiting access to just the clients you want
logged. (thus minimizing log stuffing).

it would be good to keep all the different system clocks in sync,
too.

(and NO i did not bother following the given link befre spouting off
:*)
--
William Hunt, Portland Oregon USA