From owner-freebsd-stable Fri Sep 4 14:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07384 for freebsd-stable-outgoing; Fri, 4 Sep 1998 14:16:47 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07368 for ; Fri, 4 Sep 1998 14:16:43 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id OAA12224; Fri, 4 Sep 1998 14:15:35 -0700 (PDT) (envelope-from jdp) Message-Id: <199809042115.OAA12224@austin.polstra.com> To: jason@washington.edu Subject: Re: What time shall I sup? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Date: Fri, 04 Sep 1998 14:15:35 -0700 From: John Polstra Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jason C. Wells wrote: > I am going to start supping via a weekly cronjob. I would prefer to avoid > cvsup dying because the server was too busy. It won't die. It will keep retrying until it succeeds, or until it hits the limit specified on the command line. > What is the best time of the week to run cvsup? You are not going to get a useful answer to this question. Suppose I said, "The best time to run CVSup is at 14:47 UTC on the 2nd Tuesday of each week." Then a few dozen people would all change their crontabs to run CVSup at that time, and it would suddenly become the worst time of the week to run CVSup. :-) Your best bet is to spread the load by using a mirror site other than cvsup.freebsd.org. In the US, both cvsup2 and cvsup3 are almost always less loaded than cvsup.freebsd.org. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message