From owner-freebsd-stable Wed Nov 1 12:55:17 2000 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 8026B37B4C5 for ; Wed, 1 Nov 2000 12:55:12 -0800 (PST) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA17193; Wed, 1 Nov 2000 14:55:08 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-91.max1.wa.cyberlynk.net(207.227.118.91) by peak.mountin.net via smap (V1.3) id sma017191; Wed Nov 1 14:55:01 2000 Message-Id: <4.3.2.20001101145142.00ad3a00@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Wed, 01 Nov 2000 14:54:49 -0600 To: Vivek Khera , stable@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: REMINDER: 4.2 code freeze starts tomorrow! In-Reply-To: <14848.23471.506477.393246@onceler.kciLink.com> References: <18378.973024879@winston.osd.bsdi.com> <18378.973024879@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:06 PM 11/1/00 -0500, 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 too, but only for 4.x systems. No problem with 3.x and 2.2.x systems. Vaguely recall a discussion about how this was worked around without changing the run times. A broken feature in 4.x possibly? Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message