Interesting. This is undocumented. Even not known that,, I was able to reduce the logging to what you said. Like you said however, its still like 6 lines when 1 would be sufficient ! That�s a 5 or 6 times bigger log file. Its also more I/O. I feel that better control of logging needs to be addressed. I wish I could write the code, I would submit it.
-----Original Message----- From: Michael Kolos [mailto:[EMAIL PROTECTED] Sent: Sunday, July 27, 2003 8:19 PM To: Subscribers of Qpopper Subject: Re: Several questions There is actually a pretty easy way to control what is logged and what isn't. The order in your config file is important: Everything listed before the set-tracefile is not logged. Everything listed after the set-tracefile command is. so if set-tracefile is the last thing in your config file, the volume logged is much lower. Still, there are 2 lines for each non-tls pop check (the timestamp of the start of check, and the timestamp of the stop check along with the username, process #, mail stats and IP (which is logged twice if DNS lookups are turned off). As well, TLS/SSL information is also logged, resulting in an additional 2 lines (one for TLS startup, one for TLS shutdown error) in most cases. At least all the "set" items are not logged. Michael Kolos Administrateur de R�seau Network Administrator ColbaNet Inc. NOCC_______________________________ ColbaNet - http://www.colba.net
