On Mon, Sep 01, 2014 at 06:53:49PM +1000, Dmitry Smirnov wrote: > Package: apt-cacher > Version: 1.7.9.1 > Severity: normal > > Today I found many "apt-cacher-cleanup.pl" processes run by cron on my system > so I had to knock them down with "sudo killall apt-cacher-cleanup.pl". > > To my surprise it happened despite "AUTOSTART=0" in "/etc/default/apt-cacher".
AUTOSTART only refers to the daemon process. apt-cacher-cleanup.pl is run by a cron job from /etc/cron.d/apt-cacher > Let alone reason why this process did not terminate within reasonable time > I'd > like to highlight the following problems: > > * cleaner may start multiple times if already running one(s) did not finish. That shouldn't happen as there is a lock to ensure only a single running process. If this was running on a cache directory where apt-cacher-ng was taking locks, I suspect these were not multiple instances, but the various forks that apt-cacher-cleanup.pl performs. It is supposed to run quietly and at very low priority in the background. > * cleaner runs disregarding of "AUTOSTART=0" in "/etc/default/apt-cacher". See above. > * lack of POD documentation > (i.e. "perldoc /usr/share/apt-cacher/apt-cacher-cleanup.pl" report > "No documentation found"). I accept this, but apt-cacher-cleanup.pl -h does provide something and it is also mentioned in apt-cacher(8). > I did not investigate why cleanup did not finish but I suspect that it > somehow > might be due to active "apt-cacher-ng"... > When I run "sudo /usr/share/apt-cacher/apt-cacher-cleanup.pl -v" it finished > without reporting any errors... I cannot see evidence of a real bug here. My only solution would be to prevent simultaneous installation of apt-cacher and apt-cacher-ng. Best wishes Mark -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
