[TriLUG] Another Syslogd question

[Christian J Hedemark]

I've done it successfully.

At the head end of every /etc/syslog.conf I was doing:

*.*    @loghost

The rest of the syslog.conf was mostly bone stock Red Hat issue.

I had a small number of hosts and a syslog server that was relatively idle.
Seems like a lot of logging but the machine didn't break a sweat.

This would log the default stuff locally, but EVERYTHING to the loghost.

Reverend Christian J Hedemark II
Hillsborough, NC
http://yonderway.com
"Those who are willing to sacrifice essential liberties for a little order,
will lose both and deserve neither." - Benjamin Franklin

----- Original Message -----
From: "Jeff Bollinger" <jeff01 at email.unc.edu>
To: "TriLUG" <trilug at trilug.org>
Sent: Wednesday, November 14, 2001 12:31 PM
Subject: [TriLUG] Another Syslogd question


> Is it possible to both have a machine write its logs to
> /var/log/messages AND to send them to a remote server (using straight-up
> syslog, NOT syslog-ng)?  I tried this in /etc/syslog.conf:
>
> *.info;mail.none;authpriv.none;cron.none
> /var/log/messages
> *.info;mail.none;authpriv.none;cron.none
> @syslog.server.ca
>
> and I don't think that works.  Any ideas?
>
> Thanks,
> Jeff
>
>
> --
> Jeff Bollinger
> University of North Carolina
> IT Security Analyst
> 105 Abernethy Hall
> mailto: jeff_bollinger at unc.edu
>
>
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
>