From owner-freebsd-hackers Sun Jan 21 13:14:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from icg.interactivate.com (icg.interactivate.com [207.110.42.216]) by hub.freebsd.org (Postfix) with ESMTP id 141C737B402 for ; Sun, 21 Jan 2001 13:14:12 -0800 (PST) Received: (from webmail@localhost) by icg.interactivate.com (8.11.1/8.11.1) id f0LLCkw12336; Sun, 21 Jan 2001 13:12:46 -0800 (PST) (envelope-from larry@interactivate.com) X-Authentication-Warning: icg.interactivate.com: webmail set sender to larry@interactivate.com using -f To: Sergey Babkin Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Message-ID: <980111565.3a6b50cded845@webmail.interactivate.com> Date: Sun, 21 Jan 2001 13:12:45 -0800 (PST) From: Lawrence Sica Cc: Matt Dillon , John Gregor , Gerhard.Sittig@gmx.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG, gjb@gbch.net References: <200101140244.f0E2i3518278@vieo.com> <3A621ABF.FA2C6432@bellatlantic.net> <200101142155.f0ELtLO64117@earth.backplane.com> <3A6A059C.486F6237@bellatlantic.net> In-Reply-To: <3A6A059C.486F6237@bellatlantic.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.3 X-Originating-IP: 24.20.227.61 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Sergey Babkin : > All, > > I've committed these changes for cron to support DST change > to -current (see PR bin/24494 for description of my tests). > Everyone is welcome to test them out. > Please let me know if you encounter any problems caused by them > (and better do that before these changes would be MFCed to -stable > in a few weeks). > I thought the consensus was to make it a command line feature and have the old behavior by default? Myself I get a little nervous when something as important as cron is changed without intensive testing and no way to go back to the older proven method. I'd feel alot more comfortable if these changes were made a command-line option as was discussed. I for one cannot afford cron to break on any production servers as this could literally cost my comapny thousands of dollars if scheduled tasks fail because of this change. Just my 2 cents.. --Larry > -SB > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Lawrence Sica ------------------------------------------------------------- Systems Administrator - Interactivate, Inc. larry@interactivate.com http://www.interactivate.com -------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message