> > > > > > > > http://www.mandrake.com/en/archives/cooker/2002-05/msg01166.php > > > > > > Oh yes, I read about that one. > > > > > > My personal opinion is that (as with anything fancy) that it is very > nice, > > > but it's a very big fancy candy add-on that you are adding to a > basesystem > > > tool ... > > > > True, true > > > > > You'd need to work with priorities then, the precedence of the default > sysklogd > without mysql would have to be higher, and only have it if the user requests > it. There are other things thatyou might need to take care of as well such > as rebooting from a bad system where you might not have a /usr or a network. >
there is one problem (syslog-ng hits this as well). Currently both klogd and syslogd are bundled in one package - sysklogd. You may want to replace syslog - but you definitely do not want to replace klogd. So if sysklogd maintainer would agree to split sysklogd into two packages - klogd proper and syslogd proper it would make syslogd replacements much easier. And I would immediately release syslog-ng that I have been using here for some time now without a single problem (except stupid administrator :-) I mean, with proper config and logrotate configuration that currently conflicts with syslogd logrotate. -andrej
