Hi,

> > > http://rgerhards.blogspot.com/2007/09/rsyslog-config-again.html
> > >
> > > I would deeply appreciate any feedback on the samples and format
> > > suggestions.
> > 
> > /me thinks you're getting way too little feedback on the blog, 
> > or this list. Unfortunately I don't have much more than simple
> > preference to contribute here..
> > 
> > XML-based format: 
> > 
> >     Yikes, you'll need an additional human readable frontend
> >     format that's converted to XML for it to be usable. You
> >     can't expect us poor sysadmins to be editing XML
> >     directly to configure rsyslogd..
> 
> The nice piece of this is that it is machine parseable easily  which
> enables lots of useful editors.

I don't agree with the original posters comment there also.

As an example, I have been using linuxha.net now for quite some years on many
clusters and from day one, linuxha.net has used XML for all it's configuration
files. I personally find the "standard" that brings to config files much
better than the myriad of conf files I've dealt with the many more years I've
been using UNIX and Linux.

> > syslog-ng like:
> >     
> >     Fair enough.. It works for my usage.
> 
> The syntax is okay but at that point what distinguishes b/t syslog-ng
> and rsyslog?

I've personally never been a fan of the syntax used in this. Sure I know it
now after years for admin work, but I remember the times I needed to learn it
thoroughly, it wasn't as easy as other conf files.

> > Apache like:
> > 
> >     Not sure I understand this.. Seems like a mix of option/value
> >     and xml'ish for some functionality.
> 
> This one I'm more interested in. If you think of each log like a 
> vhost and you define the qualities that are added to that inside the 
> definition
> 
> <Log mylogofsilliness>
>   Destination /path/to/silly.log
>   DestinationMode 0640
>   DestinationOwner root
>   DestinationGroup log-readers
>   Include mail.info kern.debug cron.emerg
> </Log>
> 
> etc, etc, etc
> 
> maybe that doesn't make sense, maybe it does - it is pretty easy to
> read, though.

I think every sysadmin has setup a web server and delved into the apache-like
configurations with software like apache, proftpd, etc. It's a nice and easy
to understand format which has also proved the test of time.

I'd be happy with either XML or Apache-like, but my bias is towards XML.

Regards,

Michael.

> -sv
> 
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
------- End of Original Message -------

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog

Reply via email to