M. Kellermann wrote: > At 11:51 30.04.2007, you wrote: > > >> Either way, It seems to me that this only affect logging subsystem, not >> the server itself. Am I wrong ? > > > yes - i think popper/pop_log.c does the logging - and is buggy...
The following patch shall solve this issue. But either way, this affects only logging, not server performance or security. regards JM -- --------------------------------------------------------------- Jose Marcio MARTINS DA CRUZ Tel. :(33) 01.40.51.93.41 Ecole des Mines de Paris http://j-chkmail.ensmp.fr 60, bd Saint Michel http://www.ensmp.fr/~martins 75272 - PARIS CEDEX 06 mailto:[EMAIL PROTECTED]
--- pop_log.c.org 2006-03-09 23:32:38.000000000 +0100
+++ pop_log.c 2007-04-30 13:07:28.115958000 +0200
@@ -135,7 +135,7 @@
iDateLen = strlen ( pDate ); /* length including year */
pYear = pDate + ( iDateLen - 5 ); /* point to start of year */
date_time [ iDateLen - 2 ] = '\0'; /* cut off the year */
- lMsec = (tval.tv_usec + 500) / 1000; /* convert useconds to milliseconds */
+ lMsec = tval.tv_usec / 1000; /* convert useconds to milliseconds */
fprintf ( p->trace, "%s.%03ld %.4s [%ld] %s\n",
pDate, lMsec, pYear, (long) getpid(), msgbuf );
fprintf ( p->trace, "%s.%03ld %.4s \n", pDate, lMsec, pYear );
smime.p7s
Description: S/MIME Cryptographic Signature
