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

[Matt Dillon]

: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" [EMAIL PROTECTED]

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