> 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. -- Ralf Hildebrandt (Im Auftrag des Referat V A) Ralf.Hildebrandtat_private Charite Campus Virchow-Klinikum Tel. +49 (0)30-450 570-155 Referat V A - Kommunikationsnetze - Fax. +49 (0)30-450 570-916 "Lotus Notes for Dummies" is surely a single page pull out with "don't" printed on it. --------------------------------------------------------------------- To unsubscribe, e-mail: loganalysis-unsubscribeat_private For additional commands, e-mail: loganalysis-helpat_private
This archive was generated by hypermail 2b30 : Fri Feb 01 2002 - 10:48:52 PST