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

[Matthew Seaman]

Dan Langille wrote:
> 
> 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?
> 

Howabout having a setting:

TZ=GMT0BST

or 

TZ=Europe/London

in the crontab file, analogous to the MAILTO= or USER= settings that already
exist.  That would mean individual user crontabs could run on different
timezones --- or would that just be too complicated?

I suppose the default (with no TZ= setting) should be to work just as cron
does now, using the system standard timezone, without DST hacks, or you could
choose a timezone setting without DST changes:

TZ=UTC

and probably

TZ=localtime

to use the system default time zone, with DST hacks.

        Matthew

PS.  If anyone is counting, put me down as one who thinks the DST hack is a
good idea.

-- 
           Certe, Toto, sentio nos in Kansate non iam adesse.

   Dr. Matthew Seaman, Inpharmatica Ltd, 60 Charlotte St, London, W1T 2NU
            Tel: +44 20 7631 4644 x229  Fax: +44 20 7631 4844


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message