[syslog-ng]remote logging and logfile naming

[Brian Thomas]

I'm inclined to agree with the lurker. :)

Isn't this what nscd is designed to do anyway? Wouldn't it make more sense
to recommend the use of nscd-or-equivalent if using hostname lookups?

Brian

On Tue, Mar 05, 2002 at 08:29:03AM -0600, Chad C. Walstrom wrote:
> On Tue, Mar 05, 2002 at 01:04:06PM +0100, Michael Renner wrote:
> > Baszi, would it be possible to include some sort of short-time dns
> > cache in syslog-ng, so that it'll only check for updated dns records,
> > say, every minute?
> 
> <mode value="soapbox"/>
> 
>     Including DNS cacheing into syslog-ng will not remove a point of
>     failure, it will increase the complexity of a specialized service,
>     allowing it to fail in a greater number of places.  The power of
>     UNIX programming, and one of its tennants, is in the idea that each
>     tool performs /one/ job well.  syslog-ng is optimized to receive,
>     format, and store/redirect logs from local and remote machines, and
>     it does an exceptional job.
> 
>     A local DNS cache server is designed for one job, providing a
>     system-wide service for all applications.  If it's not doing an
>     exceptional job, then concentrate on fixing that daemon, not adding
>     yet another layer of complexity to syslog-ng.
> 
>     When one starts to engineer software into virtual "swiss army
>     knives", one sacrifices the flexibility and power that the UNIX
>     programming philosophy provides.
> 
> <mode value="lurk"/>
> 
> -- 
> Chad Walstrom <chewie@wookimus.net>                 | a.k.a. ^chewie
> http://www.wookimus.net/                            | s.k.a. gunnarr
> Get my public key, ICQ#, etc. $(mailx -s 'get info' chewie@wookimus.net)