On Mon, Sep 01, 2014 at 08:11:38PM +1000, Dmitry Smirnov wrote: > Hi Mark, > > Thank you for quick reply. > > > On Mon, 1 Sep 2014 10:18:19 Mark Hindley wrote: > > > 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 > > Of course. I'm just wondering whether it make sense to run cleaner when > daemon > is disabled?
I think it does because apt-cacher can also be invoked from inetd or even in a legacy (deprecated) CGI mode. In those cases AUTOSTART is 0 but cache maintenance is required. > apt-cacher was not active for several months on this system. I assumed it > would be safe to disable daemon in "/etc/default/apt-cacher". If there is a > conflict with apt-cacher-ng then perhaps it could be considered to introduce > "conflicts" or mention the clash in README. I don't know how apt-cacher-ng handles locking, but I can imagine there may be problems if they are trying to lock files in the same cache directory at the same time. Best wishes Mark -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
