From owner-freebsd-stable  Fri Nov  3  2:58:56 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from easystreet01.easystreet.com (easystreet.com [206.26.36.40])
	by hub.freebsd.org (Postfix) with ESMTP id E6B6037B4C5
	for <stable@FreeBSD.ORG>; Fri,  3 Nov 2000 02:58:53 -0800 (PST)
Received: from easystreet.com (dsl-209-162-218-66.easystreet.com [209.162.218.66])
	by easystreet01.easystreet.com (8.9.3/8.9.3) with ESMTP id CAA27063;
	Fri, 3 Nov 2000 02:58:50 -0800 (PST)
Message-ID: <3A029A6B.FFE15663@easystreet.com>
Date: Fri, 03 Nov 2000 02:58:51 -0800
From: Bohdan Tashchuk <tashchuk@easystreet.com>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vivek Khera <khera@kciLink.com>
Cc: stable@FreeBSD.ORG
Subject: Re: REMINDER: 4.2 code freeze starts tomorrow!
References: <18378.973024879@winston.osd.bsdi.com> <14848.23471.506477.393246@onceler.kciLink.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Vivek Khera wrote:
> 
> Could the default nightly cron job time get changed to something
> outside of the 1am to 3am window?  The current time is just a bad
> default.

Hey, at least you got a discourse going.

When I raised this issue on comp.unix.bsd.freebsd.misc back in the spring,
chris@FreeBSD.org couldn't even bring himself to believe that the problem
occurs at all.

See Deja:


http://x57.deja.com/getdoc.xp?AN=605386875&CONTEXT=973248514.641662994&hitnum=2

and read the followup posts. So I won't hold my breath waiting for this to
change anytime soon.

Also for some silly reason I thought that the OpenBSD people might be
"smarter" about this. But no, their daily script runs at 1:30 and so
probably has the very same problem.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message