On Thu, 02 Oct 2014 13:53:41 -0700, grantksupport-Z02xGKUfPWYS+FvcfC7Uqw wrote:
On Thu, Oct 2, 2014, at 01:49 PM, Jim Henderson wrote:
With that many systems (assuming they're all on a common network), it seems to me the best approach would be to mirror (with rsync) the necessary repositories locally.
That's an option and a choice -- and a workaround of the issue at hand.
Whether 1 or 1000 systems are involved, zypper's failure/fallback behavior should be robust.
Sure, it should be, but at the same time, if the problem is being caused by something upstream from you, having a local repo solves the problem, and is probably the more common solution that those managing large numbers of systems use. I remember from my own days working in IT that we'd test patches from a vendor rather than let an automatic update push them out (or pull them in, depending on the platform and technology used), just in case a vendor- supplied patch broke some third party app in an unexpected way. The only way to effectively manage that was to have our own patch distribution system/system management tool separate from the OS' own tool. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org