> Our 'production' repo sits somewhat outside of the envelope expected on > this... > > We release code to production systems once per week for our > application and with the tweak done we were still seeing out of sync > behaviour of repodata, This is what an excerpt from my squid.conf > looks like on my proxies for our production environments now: > > refresh_pattern \.rpm$ 10080 100% 525960 override-expire > override-lastmod ignore-reload reload-into-ims > refresh_pattern /XMLRPC/GET-REQ/skyentprod/repodata/.*\.xml.* 0 1% 15 > refresh_pattern /XMLRPC/GET-REQ/.*/repodata/.*\.xml.*$ 0 1% 525960 > refresh_pattern . 0 100% 525960 > > As you can see we took the change that was added before but then added > a line before it to explicitly match the URI for our custom production > repo with a max lifetime of 15 minutes. This repo only changes once a > week and we have found this configuration optimised for our setup... > the 1% is not modified checks didn't work nicely for us on this due to > the long changes on updates...
OK i'll give this a bash - I wonder what will be a good max lifetime though as our repo's technically could be updated once per hour as a maximum. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
