*BSD News Article 70490


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!nntp.uio.no!Norway.EU.net!EU.net!Germany.EU.net!zib-berlin.de!irz401!uriah.heep!news
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: sup apparently crapped out badly on -stable
Date: 31 May 1996 18:22:48 GMT
Organization: Private BSD site, Dresden
Lines: 24
Message-ID: <4onddo$df@uriah.heep.sax.de>
References: <4pbb5v$iau@plains.nodak.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
NNTP-Posting-Host: localhost.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: knews 0.9.6
X-Phone: +49-351-2012 669
X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F  93 21 E0 7D F9 12 D6 4E

ortmann@plains.nodak.edu (Daniel Ortmann) wrote:

> I've run sup for quite some time without any problems, but this one
> was a pain.

Do immediately subscribe to freebsd-stable@freebsd.org.  That's what
you are expected to do when running -stable.  (Likewise goes for
-current users.)

If you were subscribed, you would have known about the breakage and
its reasons.  The large amount of data transferred by sup is a flaw in
the sup protocol.  It re-transfers entire files even if only the
timestamp has been changed.  (In this case, most of the changes were
simple CVS tag operations.)

If you can't cope with this, switch to CTM.  It requires much less
bandwidth and better optimizes these cases.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)