bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: jjudeb
Subject: Re: Runaway Memory in ipop3d on Dual-Processor XEON.
Date: Fri, 30 Jan 2004 23:24:09 -0800

JJ> I'm trying to configure a dual-processor, 
JJ> 2.4GHz Xeon box as an email server, 
JJ> running Postfix et al. under Mandrake 9.2 
 
JJ> I'm having an odd problem with two 
JJ> applications, ipop3d and imapd.  During 
JJ> login negotiation, the daemon starts 
JJ> allocating as much memory as it can, ... 
JJ> ipop3d ran up over a gigabyte of memory. 
 
I've gotten a little further. 
 
The problem affects regular Intel P4s as well, 
so it's not Xeon specific. 
 
After compiling ipop3d from scratch, I stepped 
through the execution with gdb.  The problem 
occurs when ipop3d looks up two passwd 
entries: 
 
                /* #public namespace */ 
  if (!publicHome 
         && (pw = getpwnam ("imappublic"))) 
    publicHome = cpystr (pw->pw_dir); 
                /* #shared namespace */ 
  if (!anonymous 
         && !sharedHome 
         && (pw = getpwnam ("imapshared"))) 
    sharedHome = cpystr (pw->pw_dir); 
 
 
If either of these users does not exist, then 
ipop3d goes into loop mode, and consumes all 
available memory.  If both users exist, ipop3d 
functions correctly. 
 
At this point, I don't know if the problem is 
with ipop3d or glibc or something else. 
 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]