Re: Runaway Memory in ipop3d on Dual-Processor XEON.

2004-02-01 Thread jjudeb
On Sun, 01 Feb 2004, at 20:27:38, Mark Crispin <[EMAIL PROTECTED]> wrote: MC> The idea of those calls is to enable the MC> #public and #shared namespaces if the users MC> imappublic and imapshared respectively exist. MC> Some UNIX systems don't like 10-character MC> userids, but they should

Re: Runaway Memory in ipop3d on Dual-Processor XEON.

2004-02-01 Thread Mark Crispin
I agree with you that it's a bug in your C library's implementation of getpwnam(), specifically in its NIS (a.k.a. Yellow Pages) routines (note the yp_??? function calls). The idea of those calls is to enable the #public and #shared namespaces if the users imappublic and imapshared respectively ex

Runaway Memory in ipop3d on Dual-Processor XEON.

2004-02-01 Thread jjudeb
I'm trying to configure a dual-processor, 2.4GHz Xeon box as an email server, running Postfix et al. under Mandrake 9.2 I'm having an odd problem with two applications, ipop3d and imapd. During login negotiation, the daemon starts allocating as much memory as it can, until system limits ar