From owner-freebsd-hackers Thu Jan 11 2: 9:53 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 C644237B400 for ; Thu, 11 Jan 2001 02:09:35 -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 XAA33155; Thu, 11 Jan 2001 23:08:46 +1300 (NZDT) Message-Id: <200101111008.XAA33155@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary / FreshPorts To: Greg Black Date: Thu, 11 Jan 2001 23:08:45 +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: <200101110647.TAA32661@ducky.nz.freebsd.org> of Thu, 11 Jan 2001 19:47:21 +1300 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 17:06, Greg Black wrote: > And, as I said previously, I'd want to know how the new code > coped with cron being stopped and restarted during one of the > DST transition times, as well as seeing assurances that the > legacy version would do the same thing then as it does now. If the changes are modular, and I sure hope they are, it would almost be a matter of: if newcode then call new stutt end if But I'm guessing it's going to be a *bit* more complicated than that. -- 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