Date: Tue, 23 Feb 1999 14:20:28 -0500 (EST) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: freebsd-hackers@freebsd.org Subject: inetd Output Message-ID: <199902231920.OAA26914@cc942873-a.ewndsr1.nj.home.com>
next in thread | raw e-mail | index | archive | help
[Originally sent to -questions, but I _think_ this is a better venue] I just had a really ugly problem with a mailserver at work. It's a little ol' PentiumPro with 24 MB RAM and 60 MB of swap. In hindsight, I should have given it more swap, but it never occured to me that POP and IMAP servers would be memory intensive. Someone mailed a 40+ MB file to another user. This combined with the load of some other people eating memory with IMAP and large mailspools caused the recipient of the 40+ MB file's IMAP daemon to fill the swap to the top. I had the user quit from IMAP, and I removed the big mail item using elm as root. Much credit to FreeBSD that such a situation did not cause Very Bad Things to happen, like a panic, crash, or freeze up (I know I wouldn't trust my IRIX machines to survive a full swap partition). Once I had removed the offending mail and the user's IMAP process had shutdown gracefully, I had assumed everything would be OK, but... Some bad behavior from both the inetd on the FreeBSD server, and Outlook POP and IMAP clients gave me headaches. The inetd process was returning a (this is from memory, I can't seem to find any logs of the exact message), Warning: inetd: realloc(): junk pointer too low Message to connecting clients. inetd continued to return these after the swap problem had been fixed and even after a 'killall -HUP inetd.' Further, when Outlook catches this warning message, it gives up as if it was a fatal error (which it is not, Netscape clients worked fine). I ended up fixing the problem by killing inted completely and restarting it. I did not have to restart the kernel (this machine has been up a reasonable 60 days or so). Has anyone seen behavior like this from inetd before? I occasionally get those 'junk pointer' messages on several of my FreeBSD systems for a number of different applications, is that unusual? Is there a way to stop this? I worry that junk pointer messages might be the sign of a memory leak. System info, # uname -a FreeBSD newmail.mydomain.org 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #1: Tue Dec 22 15:29:51 EST 1998 postman@newmail.mydomain.org:/usr/src/sys/compile/NEWMAIL i386 -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902231920.OAA26914>