Daniel Pittman <dan...@rimspace.net> writes:
> 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
> 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.
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
