RE: Cyrus debugging

2003-03-26 Thread Oliver Pitzeier
John Alton Tamplin wrote:
 Oliver Pitzeier wrote:
  Sorry, but I believe there are enough interessting parts in 
  imapd and 
  also in some lib/* file that could be logged for debugging reasons...
  
 Complaints about the code quality of Cyrus coming from 
 someone who tries to pass an int where a char* is expected, whose
 patch results in returning random garbage from the comparison function,
 and who can't produce a stack backtrace from the problem seems a
 bit out of place.

I'm sorry, I didn't want to _complain_. I just wanted to give feedback!
And that I passed an int to syslog was really a mistake, but comes from
programming too much Perl, where I normally do not need to think about types...

I had an idea, you don't like it. That's OK. :-)

Best regards,
 Oliver




Re: Cyrus debugging

2003-03-26 Thread Lawrence Greenfield
   Date: Wed, 26 Mar 2003 09:17:02 -0500
   From: Ken Murchison [EMAIL PROTECTED]
[...]
   The majority of imapd's work is not done in imap* files.  There are 80
   LOG_DEBUG entries in the imap/ directory, and 141 in 2.1.12.

   This is in addition to all of the LOG_INFO, LOG_NOTICE, ...  -- 990
   total!!

   I personally wouldn't want the performance of Cyrus bogged down trying
   to report every little detail to log files.

Indeed. Every syslog call does IPC which actually can be a significant
performance problem for some systems.

Additional and better logging capabilities are bug #115.

Larry