> approx-gc is run from cron and gets into an endless loop burning CPU > time and - more important - IO operations: > > # ps www 5030 > 5030 ? RN 133:10 /usr/sbin/approx-gc --quiet > > Runnings strace on the process I can see, that it repeatedly visits the same > directories again and again.
I'm guessing this is due to a symbolic link causing a loop (although the code tries to detect this, there's probably still a bug). If you can easily find the loop yourself from the strace output, or by examining "ls -lR /var/cache/approx/debian", please send me that. Otherwise just send me the output of the "ls -lR" command (need to CC the BTS since it will be large) and I'll hunt through it. > Running "approx-update --verbose" also seems to have a problem, since it > doesn't update sid/main/binary-amd64/* any more since February 22nd: > [...] > This is neither logger or reported by the daily cron job, so errors > updating the list of available packages seems to be silently ignored. > This could be critical for missed security updates. The purpose of approx-update is *not* to download new Packages files (that's the job of "apt-get update" on client machines). It just updates the state of the approx cache with respect to pdiffs. It may download some additional pdiffs if they're not already in the cache, but it won't download a new Release file or entire Packages file. So in your case, this file is shown as "valid" because it's consistent with the corresponding Release file, not because it's up-to-date with the remote archive. I'm guessing that no amd64 client machine with sid in its sources file has done an "apt-get update" recently. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
