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 dbmail-top is not going to be updated anytime soon.
Aaron On Fri, 2008-02-15 at 10:24 +0100, Paul J Stevens wrote: > 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 ./dbmail-imapd > > 29881 ? S 0:01 ./dbmail-imapd > > 29885 ? S 0:06 ./dbmail-imapd > > 29886 ? S 0:10 ./dbmail-imapd > > 29897 ? S 0:00 ./dbmail-lmtpd > > 29898 ? S 0:00 ./dbmail-lmtpd > > 29899 ? S 0:06 ./dbmail-lmtpd > > 29900 ? S 0:06 ./dbmail-lmtpd > > 29903 ? S 0:06 ./dbmail-lmtpd > > 29917 ? S 0:00 ./dbmail-pop3d > > 29918 ? S 0:00 ./dbmail-pop3d > > 29919 ? S 0:17 ./dbmail-pop3d > > 29921 ? S 0:00 ./dbmail-pop3d > > 29923 ? S 0:00 ./dbmail-pop3d > > 30670 ? S 0:00 ./dbmail-imapd > > > > > > DBMail top utility -- Update interval 3 sec -- Press Q to quit > > Daemons found or (not found):*** glibc detected *** malloc(): memory > > corruption: 0x0000000000541b10 *** > > > > > > Aborted > > > > > > Paul J Stevens пишет: > >> Thank you for taking an interest in dbmail. > >> > >> These messages are 'normal' in 2.2 and 2.3.2, but they will be gone in > >> 2.3.3. > >> > >> As far as I know, they are 'false positives' and don't actually mean > >> trouble. > >> > >> > >> Bokhan Artem wrote: > >> > >>> 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] > >>> imap4.c,IMAPClientHandler(+319): command return with error [idle] > >>> Feb 12 16:23:25 art dbmail-imapd[3180]: Error:[imap] > >>> imap4.c,IMAPClientHandler(+319): command return with error [idle] > >>> Feb 12 16:27:19 art dbmail-imapd[3293]: Error:[imap] > >>> imap4.c,IMAPClientHandler(+155): [Illegal seek] on read-stream > >>> > >>> > >>> Bokhan Artem пишет: > >>> > >>>> I'm a newbie with dbmail, so I'm beginning to ask my stupid questions > >>>> while testing :) > >>>> Is that normal behaviour? > >>>> > >>>> Feb 12 15:57:08 art dbmail-imapd[3176]: Error:[imap] > >>>> imap4.c,IMAPClientHandler(+155): [Illegal seek] on read-stream > >>>> Feb 12 15:59:03 art dbmail-imapd[3176]: Error:[imap] > >>>> imap4.c,IMAPClientHandler(+155): [Illegal seek] on read-stream > >>>> Feb 12 15:59:04 art dbmail-imapd[3176]: Error:[imapsession] > >>>> dbmail-imapsession.c,dbmail_imap_session_printf(+1488): write to > >>>> client socket failed > >>>> Feb 12 15:59:36 art dbmail-imapd[3174]: Error:[imapsession] > >>>> dbmail-imapsession.c,dbmail_imap_session_printf(+1488): write to > >>>> client socket failed > >>>> > >>>> _______________________________________________ > >>>> DBmail mailing list > >>>> [email protected] > >>>> https://mailman.fastxs.nl/mailman/listinfo/dbmail > >>>> > >>> _______________________________________________ > >>> DBmail mailing list > >>> [email protected] > >>> https://mailman.fastxs.nl/mailman/listinfo/dbmail > >>> > >>> > >> > >> > >> > > > > _______________________________________________ > > DBmail mailing list > > [email protected] > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
