Re: bind syslogd to certain network interface only

From: Denis Zaitsev <zzz@anda.ru>
Date: Mon Feb 14 2005 - 09:49:02 CET

On Mon, Feb 14, 2005 at 09:18:27AM +0100, Martin Schulze wrote:
> Denis Zaitsev wrote:
> > On Mon, Feb 14, 2005 at 08:50:30AM +0100, Martin Schulze wrote:
> > > Denis Zaitsev wrote:
> > > > Are there any plans to add an ability to syslogd to listen on just one
> > > > or some network addresses of a machine? This way it would be possible
> > > > to have more than one syslog daemon running on the host and listening
> > > > its own subnet etc. Or this scheme would be undesirable for some
> > > > reason?
> > >
> > > Maybe.
> >
> > And what drawbacks it possible will introduce?
>
> Cluttering the code, feature bloat.

Ok... From the other side, the feature seems to be healthy. Why do
you think it hasn't still been implemented? Is it very uncommon to
gather logs from the different network segments on the one log server?
Or some better approach should be used there?
Received on Mon, 14 Feb 2005 13:49:02 +0500

This archive was generated by hypermail 2.1.8 : Mon Feb 14 2005 - 09:49:20 CET