On Mon 05 Oct 2026 at 06:29:12 (-0600), Charles Curley wrote: > On Sun, 4 Oct 2026 20:29:59 -0400 > Dan Purgert <[email protected]> wrote: > > On Oct 04, 2026, Charles Curley wrote: > > > How do I tell which apt cache did I use, if any, when running "apt > > > update" or "apt upgrade"? I use auto-apt-proxy to detect apt > > > proxies. > > > > If I'm reading the question correctly, your system will use the > > repository configured in /etc/apt/sources.list (or, if you're using > > the newer format, I think it's /etc/apt/xxx.sources -- although > > ILately haven't done a new-install yet, so I don't know the exact > > filename) > > > > Unless your network integrates a proxy (e.g. I dunno, a university > > campus), then chances are there is no proxy. > > Sorry for the lack of context. I've been running a small office/home > (SOHO) network for several decades, starting in dial-up modem days, and > that has included an apt proxy server since then. Lately I have been > running apt-cacher-ng, and I am experimenting with apt-cacher-ultra. I > use auto-apt-proxy to detect the proxy. So the question is, did a given > run of apt use a proxy, and if so which one?
I only know about apt-cacher-ng, which logs its use in /var/log/apt-cacher-ng/apt-cacher.log, helping you to distinguish between two potential servers. A routine update where there's been no change in the lists, run on behalf of the serving host itself: 1791198001|I|757|127.0.0.1|debrep/dists/trixie/InRelease 1791198001|O|102|127.0.0.1|debrep/dists/trixie/InRelease 1791198001|I|44891|127.0.0.1|secdeb/dists/trixie-security/InRelease 1791198001|O|43688|127.0.0.1|secdeb/dists/trixie-security/InRelease 1791198001|I|48744|127.0.0.1|debrep/dists/trixie-updates/InRelease 1791198001|O|47609|127.0.0.1|debrep/dists/trixie-updates/InRelease AIUI: secs since epoch|In Out|bytes|IPaddr|file concerned. An update, and a chromium upgrade for a client machine: 1790915127|I|757|192.168.1.17|debrep/dists/trixie/InRelease 1790915127|O|102|192.168.1.17|debrep/dists/trixie/InRelease 1790915127|I|789|192.168.1.17|secdeb/dists/trixie-security/InRelease 1790915127|O|43688|192.168.1.17|secdeb/dists/trixie-security/InRelease 1790915127|I|240262|192.168.1.17|secdeb/dists/trixie-security/main/source/by-hash/SHA256/944 … 1790915127|O|239126|192.168.1.17|secdeb/dists/trixie-security/main/source/by-hash/SHA256/944 … 1790915127|O|263864|192.168.1.17|secdeb/dists/trixie-security/main/binary-amd64/by-hash/SHA2 … 1790915127|I|751|192.168.1.17|debrep/dists/trixie-updates/InRelease 1790915127|O|47609|192.168.1.17|debrep/dists/trixie-updates/InRelease 1790915138|O|8788260|192.168.1.17|secdeb/pool/updates/main/c/chromium/chromium-l10n_154.0.80 … 1790915141|O|90614258|192.168.1.17|secdeb/pool/updates/main/c/chromium/chromium_154.0.8037.9 … 1790915141|O|30605229|192.168.1.17|secdeb/pool/updates/main/c/chromium/chromium-common_154.0 … 1790915141|O|283691|192.168.1.17|secdeb/pool/updates/main/libp/libpng1.6/libpng16-16t64_1.6. … The timestamps should coincide with APT's logs on the client. Cheers, David.
