glibc or dbmail bug?
Debian etch
ps ax | grep dbmail
29878 ?S 0:00 ./dbmail-imapd
29879 ?S 0:00 ./dbmail-imapd
29881 ?S 0:01 ./dbmail-imapd
29885 ?S 0:06 ./dbmail-imapd
29886 ?S 0:10 ./dbmail-imapd
29897 ?S 0:00
Don't use dbmail-top. It was never actually finished. And with the rewritten
server core going into 2.3.3 it will have to be removed.
Bokhan Artem wrote:
glibc or dbmail bug?
Debian etch
ps ax | grep dbmail
29878 ?S 0:00 ./dbmail-imapd
29879 ?S 0:00
With the new architecture, I think that a completely different approach
to status monitoring makes more sense, dedicating a thread to talking to
the monitoring agent (i.e., dbmail-top) -- but yes, Paul's been moving
much faster on the fantastic threading than I have even had time to look
at it, so
lmtpd uses a lot of memory after sending about 4k messages with 1Mb size
what's the reason?
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
30933 nobody15 0 463m 438m 1764 S 24 11.1 0:53.71 dbmail-lmtpd
30934 nobody15 0 447m 422m 1764 S 14 10.7 0:52.30
Feb 12 16:21:40 art dbmail-imapd[3180]: Error:[imap]
imap4.c,IMAPClientHandler(+155): [Illegal seek] on read-stream
Feb 12 16:23:10 art dbmail-imapd[3282]: Error:[imap]
imap4.c,IMAPClientHandler(+155): [Illegal seek] on read-stream
Feb 12 16:23:25 art dbmail-imapd[3282]: Error:[imap]