Date: Sat, 3 Feb 1996 13:09:53 -0500 (EST) From: Kim Culhan <kimc@w8hd.org> To: hackers@freebsd.org Subject: sup is broken? Message-ID: <Pine.BSF.3.91.960203125915.304F-100000@moonpie.w8hd.org>
next in thread | raw e-mail | index | archive | help
I have been trying for many hours to sup -stable and am becoming convinced it is not possible. The most recent attempt of a few minutes ago illustrates the main problem: I start the sup process and it successfully updates up to a point where we see something like: SUP Updated directory secure SUP Upgrade of src-secure-stable completed at Feb 3 12:58:59 1996 SUP Created directory sup/src-secure for sup/src-secure/when.stable SUP Upgrade of src-share-stable at Sat Feb 3 12:59:00 1996 SUP Fileserver 9.13 (4.3 BSD) 16381 on freefall.FreeBSD.org at 12:59:00 SUP Fileserver supports compression. SUP Fileserver is currently busy SUP: Will retry in 85 seconds SUP Fileserver 9.13 (4.3 BSD) 16508 on freefall.FreeBSD.org at 13:00:26 SUP Fileserver supports compression. SUP Fileserver is currently busy SUP: Will retry in 189 seconds During that little window in time between the point when: SUP Upgrade of src-secure-stable completed at Feb 3 12:58:59 1996 and SUP Upgrade of src-share-stable at Sat Feb 3 12:59:00 1996 the sup server became busy. From recent experience this will continue to back-off in retry time, effectively hanging it for the next several hours. Alas.. if only it would have hung in there for another couple minutes.. 8 minutes later and the back-off time is now 528 seconds. I think I looked everywhere for a list of alternate servers but could not find it. Is there any way around this? Any thoughts are greatly appreciated. regards kim -- kimc@w8hd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960203125915.304F-100000>