On Mon, Oct 05, 2026 at 02:30:59PM -0500, David Wright wrote: [...]
> > I had a look at an apt client, and at least in /var/log/apt I can't find > > any trace of the cache. It seems APT doesn't know about it (after passing > > it to the HTTP library). > > That's right, and that's the OP's problem. But what the APT client > does log is (using as an example the same instance in my post above): Thanks for confirming. That means that to know (or at least to nearly-know) you need access to the cache's logs themselves... [...] Thanks for this nice cross-log analysis :-) > So I'm using timings to tie the client to the server/proxy pair. > I would presume that a proxy not selected by auto-apt-proxy would > show no evidence of its being hit. Repeating my disclaimer, I only > know what apt-cacher-ng logs, and not what other cachers record. > > Unlike some others here, apt-cacher-ng hasn't given me cause to > look at apt-cacher-ultra. Any problems I've had in the past can > usually be put down to running apt-cacher-ng on a system that's > serving clients one or even two Debian versions ahead, something > I'm trying to avoid nowadays. FWIW, it's my favourite proxy, too. And sometimes I do experiment wit other architectures and similar stuff. A real time saver and works like a charm. Cheers -- t
signature.asc
Description: PGP signature
