Quoting Magosanyi Arpad ([EMAIL PROTECTED]) on Wed, Oct 20, 1999 at 01:10:15PM
+0200:
> A levelez?m azt hiszi, hogy Volker Wiegand a k�vetkez?eket �rta:
>
> > Generally I think the beast should have a new name, but still be able to
> > be recognised. As far as I can see, SyslogNG has already been taken. So I
> > vote for NSyslog, being short for "New Syslog", if that is still free. A
>
> It is taken by Darren. Actually it is the precursor of syslog-ng.
syslog2 is fine for me.
> > On network connections:
> > Currently syslog uses UDP only. Of course we should keep UDP. It is quite
>
> We should keep UDP only for backward compatibility IMHO.
Yes please!
> > On extensibility:
> > We all agree that the current bitmask design is way too inflexible. We
> > also want to be able to include new facilities as they are needed. My
> > suggestion is a list maintained the same way as the TCP port assignment.
> > [Excursion into implementation: you want a local /etc/facilities, which
> > can also be implemented with a NIS map, an LDAP service or anything that
> > can empower it like /etc/services]. The list shall be maintained by IANA.
> > The current bit masked values could more or less easily be integrated.
>
> Interesting idea.
> I would better like a name than a number. I guess most of the facility
> names are local to your logging system, and also have some sort of
> structure (e.g. "firewall/ftp-proxy/from-here-to-there").
Log files would get awfully verbose then. and I typically see several meg of
log entries per day on a typical DMZ environment.
Having a /etc/facilities file that can be user extended (with decent defaults
in a fiven range) should be easy to set up.
> > On backward compatibility:
> > A challange, indeed. Within the local machine this touches the config file
> > and the output format, and of course the daemons. I would like to keep the
> > basic /etc/syslog.conf design, but have more flexibility in extending it.
> > Several current approaches use braces after the facility+severity. To be
> > honest, I dislike this. Limits the number of extensions and actually voids
> > the readability. My proposal is a "continuation record", disguised as a
> > comment with a marker. Sorry if this is already talking implementation.
>
> I am quite happy with syslog-ng's log format. The syslog.conf format is
> a way too simple.
I do like the syslog-ng format. Easy to extend and still readable. See also
named.conf.
cheers
afx
--
SuSE Muenchen GmbH Phone: +49-89-42769-0
Stahlgruberring 28 Fax: +49-89-42017701
D-81829 Muenchen, Germany
May the Source be with you!
