On 1 February 2002, Ralf Hildebrandt <Ralf.Hildebrandtat_private> wrote: > > The point of this? Well, it's clear that it's quite possible to get > > high levels of logging, even from multiple clients to the one log > > daemon, provided we're not using syslogd and UDP. My logger would > > need a bit of work before it could go into service in a production > > environment, but I think it serves to show that solving the logging > > problem is not really all that hard. > > > > What would be needed to bring this toy program up to a level where > > it could replace syslogd? Since I'd be happy to use multilog to > > do the actual log writing and rotation, as it already does that > > really well, the daemon would only need a bit of code for handling > > potential errors more robustly and it would pay to profile the code > > that collects the complete lines, as that was a really quick hack. > > The other part of the job would be to re-implement syslog(3) and > > friends to do talk TCP with this daemon -- I'd say less than a day's > > work for a competent programmer. > > Gerrit Pape has already written that (I think): socklog. Incidentally, I looked at socklog a few weeks ago. It's not exactly the cleanest written program I've ever seen. In fact, I found a bug so embarrasing that I'll never let it handle such a critical operation as logging. (Yes, I did send the author a bug report.) Regards, Liviu Daia -- Dr. Liviu Daia e-mail: Liviu.Daiaat_private Institute of Mathematics web page: http://www.imar.ro/~daia of the Romanian Academy PGP key: http://www.imar.ro/~daia/daia.asc --------------------------------------------------------------------- To unsubscribe, e-mail: loganalysis-unsubscribeat_private For additional commands, e-mail: loganalysis-helpat_private
This archive was generated by hypermail 2b30 : Sat Feb 02 2002 - 18:05:37 PST