From owner-freebsd-hackers Wed Jan 10 0:20:36 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 B9A3237B404; Wed, 10 Jan 2001 00:20:17 -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 VAA28529; Wed, 10 Jan 2001 21:20:14 +1300 (NZDT) Message-Id: <200101100820.VAA28529@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: Doug Barton Date: Wed, 10 Jan 2001 21:20:13 +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: <3A5B5656.E2AAF0B5@FreeBSD.org> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Jan 2001, at 10:20, Doug Barton wrote: > > And when you finally realize that everyone else thinks this is a great > > idea, I do not like being included in "everyone". I don't think it's a great idea. > > In fact, I'm quite sure that this is not true. I happen to be the only one > who is currently voicing opposition. IMHO, the solution is not to schedule jobs during during the changeover period. However, *if* the mods are adopted, it should default to off. Add a switch to turn them on. See how that runs for a few years. Then, and only then, if the feedback is positive, consider changing it to the default behaviour. Such a radical change to cron cannot be implemented without sufficient field testing. That will take years. It cannot be simulated. -- 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