On Monday 19 July 2004 23:13, Fred might have typed: > Gary Smith wrote: > > Even after the problem has been fixed with RDJ it will just mask the > > fact that we cannot connect to the server. Basically, we will never > > know that it failed because no update occured. > > True, however, in my cron scripts I am alerted of errors or output from any > script which is run. If you check the output of those scripts you will see > when things go bad. > > I'm a member of SARE and I'm all for the ratelimiter. we spend a great > deal of time and effort doing our thing and some admins are irresponsible > enough to set updates for once every 2 minutes. We have to protect
Gentoo's portage has a neat feature that may work for the ratelimiting for the rulesets. When emerge sync is run, a single small file is retrieved (couple of bytes if I remember right), and this file is apparently compared to the on-disk copy. If the contents are different (I think the file has a unix timestamp in it), the full sync occurs, updating the portage tree with rsync. If the contents are the same, the sync exits cleanly. A similar function could be achieved with wget. It doesn't stop the 'every 2 minutes' folks, but it should help reduce the transfer load. When a new ruleset is loaded, or updated, the timestamp file gets incremented. RDJ can then use that file to determine if it needs to pull files or not.
