(I think this has been mentioned before.)
Do these hurt?:
May 2 13:41:30 sysname dovecot: POP3(xxxx): madvise() failed with
file /users/xx/xxxx/Maildir/dovecot.index.log: Operation not
supported
I think not, since I've been seeing them forever. But they do muddy the
logs. This is on an old BSD/OS server, where the man page for madvise
ends with:
BUGS
This call is not yet supported.
The messages are *only* about index.log files.
Would it be possible to either suppress the log message if the error is
specifically "not supported" or, better yet, detect it at configure
time?
Completely understandable if it's not worth the effort, though.
mm
On Tue, 2006-05-02 at 13:47 -0400, Mark E. Mallett wrote:> (I think this has been mentioned before.) > > Do these hurt?: > > May 2 13:41:30 sysname dovecot: POP3(xxxx): madvise() failed with > file /users/xx/xxxx/Maildir/dovecot.index.log: Operation not > supportedNope.> Would it be possible to either suppress the log message if the error is > specifically "not supported" or, better yet, detect it at configure time? > > Completely understandable if it's not worth the effort, though.Maybe just remember to remove #define HAVE_MADVISE from config.h after configure? :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20060502/45828741/attachment.bin>