-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 11, 2002 at 2141 +0000, Tina Bird appeared and said: > On Wed, 11 Dec 2002, Marcus J. Ranum wrote: > > > If we want to achieve "bang for the buck" in syslogging, > > we'd worry less about the transport and more about the > > contents of what is initially logged. [...] > [...] > Although changing every bit of app code out there is an overwhelming > prospect, I have it on Good Authority that at least a couple of my buddies > in the open source community are implementing a few of my ideas about > things that Should Be Logged. I'm trying to write up a summary of where > the list left the conversation so we can publish something. I think this is a good idea because developers might need some idea on how to succeed in the Fine Art of Logging. Most programs contain debug code anyway (at least the ones with good code). Do you think that developing a kind of log library or log module would be sensible in this context? People tend to read the docs if they encounter an API or something similar. Which approach do your free/open source buddies use? Curious, Lynx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE998TOeMu5lRpXJ7kRAoPqAJwMOsLUD7PS6KxIEjsGZ7IhEnUr9ACgoUMk IKmiVlHPvOuFMUgTodmMKZA= =lhKg -----END PGP SIGNATURE----- _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Wed Dec 11 2002 - 16:40:24 PST