severity 593356 serious thanks #include <hallo.h> * Daniel Pittman [Thu, Aug 19 2010, 04:29:24PM]:
> > We use apt-cacher-ng in the office to reduce the cost of updates, for which > > it works great. However, after moving from an Etch machine to a Lenny .oO( https://flattr.com/thing/51105/Apt-Cacher-NG is the place to say Thanks! ) > > machine running apt-cacher-ng we hit trouble with memory exhaustion. > > [...] > > > It turns out that the troublesome setting is: > > MaxStandbyConThreads: 2 > > > > With that enabled, memory leak, with it commented out, nothing. > > Sadly, this turns out to be untrue: with this setting enabled I can reproduce > the leak using a local loop of 'aptitude update' calls; with it disabled the > problem hides from that, but still shows up as our remote machines perform > their updates through the day. I found a couple of issues which might cause the leak. I will send you a current development snapshot tonight. In the meantime, could you please check which resources are leaked? File handles? lsof -n | grep apt-ca Processess/Threads/Memory? ps aux -L | grep apt-ca Regards, Eduard. -- <HE> Argh, ich kann nicht parsen. * HE müsste halt regelmässiger in die Compilerbau-VL gehen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
