From owner-freebsd-hackers Wed Jan 10 22:48:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 5E8A237B402 for ; Wed, 10 Jan 2001 22:48:07 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id TAA32661; Thu, 11 Jan 2001 19:47:25 +1300 (NZDT) Message-Id: <200101110647.TAA32661@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: Greg Black Date: Thu, 11 Jan 2001 19:47:21 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Reply-To: dan@langille.org Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: References: <20010110233907.L253@speedy.gsinet> of Wed, 10 Jan 2001 23:39:07 +0100 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11 Jan 2001, at 16:33, Greg Black wrote: > We'd need some guarantees that the attempt to maintain current > behaviour was done correctly -- i.e., without introducing bugs > that broke things. What sort of guarantees are acceptable? > In the beginning, something like CRON_DST_HACK="NO" in rc.conf > with a comment pointing to the explanation should cover both > these items. If more is needed later, then it can be added. Do you mean /etc/defaults/rc.conf? -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ FreshPorts - http://freshports.org/ NZ Broadband - http://unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message