Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab)

[Dan Langille]

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message