Hello guys,
if you have still means to reproduce the mentioned behavior, I have a
test version (unofficial 0.7.14pre1) which should avoid such loops for
sure. It also eliminates a couple of possible scenarios that may have
caused the looping itself... and if the reason is still there, it will
tell
Hallo,
* Eric [Mon, Jul 01 2013, 01:17:29PM]:
> I am having the exact same problem with apt-cacher-ng eating 25% of
> the CPU as the original reporter. I am running Debian Wheezy.
>
> The runaway cpu usage starts after the the daily cron job is
> launched if apt-cacher-ng has been running for mul
I am having the exact same problem with apt-cacher-ng eating 25% of the
CPU as the original reporter. I am running Debian Wheezy.
The runaway cpu usage starts after the the daily cron job is launched if
apt-cacher-ng has been running for multiple hours.
Here is an strace I get when its loop
3 matches
Mail list logo
