To clarify, I meant run 1x while they work on the issue or until we fix sa-update. Sa-update should be able to run more often. Regards, KAM
"Daryl C. W. O'Shea" <[email protected]> wrote: On 26/08/2011 10:37 PM, Kevin A. McGrail wrote: > I don't think we need anything that official. We are trying to fix a > legitimate problem and I believe their IT people will be interested in > trying to resolve the issue. At worst, they can modify their cron to > only try 1x per day. I'm -1 on asking people to only run sa-update once a day. I have no issue with it being run hourly (or more). I would encourage people to run it more than once a day. Frequent runs of sa-update means a faster automatic time to recovery from a bad sa-update update release. If we tell/make people only run it once a day they have the very likely potential to have a busted/bad update for a day or two. So long as sa-update is not broken (temp file issue sounds like a possible broken-bit) we can control the impact on our DNS servers with TTLs. Impact on mirrors should be controlled by the frequency of update releases. Essentially... we control everything. If people want to run sa-update */5, that's fine by me. I think I run all of mine */15. Daryl
