![]() ![]() I found this tutorial: How to cache openSUSE repositories with Squid. Packages are downloaded using segmented downloading spread over multiple mirrors, which together makes it impossible for squid to do much caching. This link in this answer provides the information why squid does not work well here: The repositories are http, not https thus there should not be a problem for a proxy. Even if for some strange reasons the Linux systems would access different servers (Is there some kind of DNS-intransparent redirection?) then I would expect the proxy storage to be at least as big as the biggest download. The access.log shows both hits and misses. But the squid storage directory contains only about 80 MiB data. What I don't understand: After a distro upgrade the first online update is supposed to be 400 MiB to 700 MiB (that's what YaST says before starting the update). tcpdump shows that the other systems access the proxy and the proxy accesses the repositories. Its only purpose is to prevent that all the Linux systems (openSUSE) download their updates from the Internet.Ī proxy can easily be configured for the openSUSE update tool. With no previous experience I have just set up a squid proxy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |