On Tue, 2 Jul 2002, P a u l Guth wrote: > The response from the coders has been basically "Everything > you want you can get from looking in the database."
what if the database goes down? code is not perfect. what if, for some unforseen reason, the data in the database ends up _not_ being representative of what is going on with the system? from an operational point of view, not logging is just silly. plus, logging to syslog can help identify interactions between your software and the system that might not otherwise be apparant. logging is cheap, from a coding point of view. having to interact with a database in order to determine what is going on with the system takes too much work, and involves writing additional code that in and of itself may be buggy. i question any complex development project that doesn't include, at a bare minimum, debug logging via syslog or a flat logfile. -- christian void - [EMAIL PROTECTED] www.morphine.com/void/ gpg key available on request jay is my hero. _______________________________________________ Bits mailing list [EMAIL PROTECTED] http://www.sugoi.org/mailman/listinfo/bits
