From owner-freebsd-current  Wed Feb  7 00:14:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA09084
          for current-outgoing; Wed, 7 Feb 1996 00:14:08 -0800 (PST)
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09077
          Wed, 7 Feb 1996 00:13:54 -0800 (PST)
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id TAA21647; Wed, 7 Feb 1996 19:12:46 +1100
From: michael butler <imb@scgt.oz.au>
Message-Id: <199602070812.TAA21647@asstdc.scgt.oz.au>
Subject: Re: sup%d is broken - I agree
To: uhclem@nemesis.lonestar.org (Frank Durda IV)
Date: Wed, 7 Feb 1996 19:12:45 +1100 (EST)
Cc: hackers@freebsd.org, current@freebsd.org
In-Reply-To: <m0tjz3q-000CCzC@nemesis.lonestar.org> from "Frank Durda IV" at Feb 6, 96 07:52:00 pm
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
Precedence: bulk

Frank Durda IV writes:

> Since your assumption that problems getting into sup.freebsd.org is one
> cause of sup2-n being "strange", ..

This is probably a symptom of the disease itself .. the more heavily loaded
freefall becomes, the less likely it is that mirrors will be able to get in
and out quickly with coherent source trees. Then, as people realise the
inconsistencies, they come back again (and again) to get the bits they think
are wrong .. the problem just exponentiates.

> why not do the following:

 [ .. lots of constructive suggestions .. ]
 
It depends on where the load is .. if it's CPU and network related rather
than disk, is it not possible to (NQ?)NFS-mount the relevant pieces of
freefall's file structure and offer it to the mirrors via a separate
interface and IP number or is the load of running an NFS server worse than
the original disease ?

	michael