From owner-freebsd-stable Wed Nov 1 12:58:28 2000 Delivered-To: freebsd-stable@freebsd.org Received: from krycek.zoominternet.net (krycek.zoominternet.net [63.67.120.9]) by hub.freebsd.org (Postfix) with SMTP id 5CE9B37B4C5 for ; Wed, 1 Nov 2000 12:58:25 -0800 (PST) Received: (qmail 17421 invoked from network); 1 Nov 2000 20:56:55 -0000 Received: from lcl12.cvzoom.net (208.226.155.12) by krycek.zoominternet.net with SMTP; 1 Nov 2000 20:56:55 -0000 Date: Wed, 1 Nov 2000 15:58:24 -0500 (EST) From: Donn Miller To: Yaroslav Halchinsky Cc: freebsd-stable@FreeBSD.ORG Subject: Re: REMINDER: 4.2 code freeze starts tomorrow! In-Reply-To: <20001101205246.E83DD2FA0C@relay1.ntu-kpi.kiev.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Nov 2000, Yaroslav Halchinsky wrote: > Vivek Khera wrote: > > There's one "bad" default that might like to get changed. That is the > > time that cron runs the daily scripts. The current setting in > > /etc/crontab is 1:59 in the morning. Well, last Sunday that time > > occurred twice as we switched from daylight to standard time. The > > times between 1am and 3am should be avoided for any system cron jobs > > just because of this problem. Yep, happened here as well. I live in PA. > > 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. > Here we changed from daylight time at 4:00am. So? I think this whole "2 A.M." thing should be later in the moring as well. I think Slackware runs a similar daily cron job at something like 4:40 AM or thereabouts. I think we should have the 2AM thing moved to 4:01 AM, because a lot of people are still up and working at their computers at 2 AM. It's very inconvenient. (Man, I HATE that daily thing!) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message