From owner-freebsd-hackers Fri Jan 19 13:32:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth.backplane.com [208.161.114.65]) by hub.freebsd.org (Postfix) with ESMTP id 6C23F37B400 for ; Fri, 19 Jan 2001 13:32:17 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0JKinl97875; Fri, 19 Jan 2001 12:44:49 -0800 (PST) (envelope-from dillon) Date: Fri, 19 Jan 2001 12:44:49 -0800 (PST) From: Matt Dillon Message-Id: <200101192044.f0JKinl97875@earth.backplane.com> To: Gerhard Sittig Cc: Greg Black , freebsd-hackers@FreeBSD.ORG Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) References: <20001220211548.T253@speedy.gsinet> <3A513799.75EAB470@FreeBSD.org> <20010102133239.V253@speedy.gsinet> <20010107170840.G253@speedy.gsinet> <3A5AE490.D251F590@gorean.org> <20010109124044.A16276@mithrandr.moria.org> <3A5B5656.E2AAF0B5@FreeBSD.org> <20010116192601.B253@speedy.gsinet> <20010117184854.G253@speedy.gsinet> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm just editing the PR with the cron patches to "catch up" with :OpenBSD in this respect (stating that it doesn't handle DST, but :has benefits whenever one's clock is jumping or cron waking up :too late and _could_ be extended to handle DST). Therein I :suggest to :- not touch current cron at all but switch to a different : executable by means of the newly introduced rc.conf variables : or to :- modify cron but make the new code optional while defaulting to : off :(in this order). Although I cannot say which variant will happen :driven by those with enough priviledges to decide and commit. As :well as I cannot even tell you if something will be done at all :in the near future regarding the fact that there's no DST :solution available yet -- which was the actual reason for the :wish to change something. : :virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 :Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net In the second suggestion, I presume turned off by default but can be turned on with a command-line option? (Verses a make.conf compile-time variable). I like the idea of a command-line option to turn on the 'new' code. That provides a consistent, straightforward way of allowing developers to test the code, making it available in releases with a simple rc.conf twitch, and eventually (years later judging by the flame war:-)) turning it on in /etc/defaults/rc.conf. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message