From owner-freebsd-hackers Wed Jan 17 12:25: 6 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 6210937B698 for ; Wed, 17 Jan 2001 12:24:46 -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 JAA10303; Thu, 18 Jan 2001 09:24:40 +1300 (NZDT) Message-Id: <200101172024.JAA10303@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: Gerhard Sittig Date: Thu, 18 Jan 2001 09:24:39 +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: <20010117184854.G253@speedy.gsinet> References: ; from gjb@gbch.net on Wed, Jan 17, 2001 at 06:43:31AM +1000 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Jan 2001, at 18:48, Gerhard Sittig wrote: > 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 This is the safest route IMHO. No risk for that that choose not to use it. -- 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