From owner-freebsd-stable Wed Nov 1 12:52:53 2000 Delivered-To: freebsd-stable@freebsd.org Received: from relay1.ntu-kpi.kiev.ua (www.ntu-kpi.kiev.ua [212.111.192.161]) by hub.freebsd.org (Postfix) with ESMTP id D7CDB37B65E for ; Wed, 1 Nov 2000 12:52:50 -0800 (PST) Received: by relay1.ntu-kpi.kiev.ua (Postfix, from userid 1122) id E83DD2FA0C; Wed, 1 Nov 2000 22:52:46 +0200 (EET) From: Yaroslav Halchinsky To: freebsd-stable@freebsd.org Subject: Re: REMINDER: 4.2 code freeze starts tomorrow! In-Reply-To: <14848.23471.506477.393246@onceler.kciLink.com> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/4.1-STABLE (i386)) Message-Id: <20001101205246.E83DD2FA0C@relay1.ntu-kpi.kiev.ua> Date: Wed, 1 Nov 2000 22:52:46 +0200 (EET) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. > 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? -- Regards, Yaroslav Halchinsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message