Done...
I will report if the problem remains.

root@internal-services:~# dpkg -i apt-cacher-ng_0.7.12-1_i386.deb
(Reading database ... 34645 files and directories currently installed.)
Preparing to replace apt-cacher-ng 0.7.11-1 (using
apt-cacher-ng_0.7.12-1_i386.deb) ...
[ ok ] Stopping apt-cacher-ng: apt-cacher-ng.
Unpacking replacement apt-cacher-ng ...
Setting up apt-cacher-ng (0.7.12-1) ...

Configuration file `/etc/apt-cacher-ng/acng.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** acng.conf (Y/I/N/O/D/Z) [default=N] ?
[ ok ] Starting apt-cacher-ng: apt-cacher-ng.
Processing triggers for man-db ...




On Tue, May 14, 2013 at 6:56 PM, Eduard Bloch <e...@gmx.de> wrote:

> Hallo,
> * Alexander Muthmann [Mon, May 13 2013, 09:00:38AM]:
> > I can confirm this bug on my wheezy system.
> >
> > Each morning my apt-cacher-ng system starts some processing and CPU usage
> > goes up to ~30%. The process lasts at least 2 days ( i killed it
> > afterwards).
> >
> > As the system is monitored, i can tell some things:
> > There is no increase of Disk IO but the number open inodes goes up from
> 7k
> > to 15k and the numberof threads goes up by ~70.
> >
> >
> > strace:
> >
> > [pid  2696] time(NULL)                  = 1368427918
> > [pid  2696] time(NULL)                  = 1368427918
> > [pid  2696] time(NULL)                  = 1368427918
> > [pid  2696] time(NULL)                  = 1368427918
> > [pid  2696] time(NULL)                  = 1368427918
> > [pid  2696] select(1, [], NULL, NULL, {0, 1}) = 0 (Timeout)
>
> Thanks. I have a pretty good idea where this happens but not exactly how
> the triggering conditions look like, therefore the fix is not obvious.
>
> If that's reproducible, maybe you could test the Experimental version,
> i.e. 0.7.12-1 from the Debian archive? (won't install without curl or
> wget installed, known bug, sorry)
>
> Regards,
> Eduard.
>

Reply via email to