From owner-freebsd-hackers Tue Apr 7 07:52:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04643 for freebsd-hackers-outgoing; Tue, 7 Apr 1998 07:52:27 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04638 for ; Tue, 7 Apr 1998 07:52:21 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id HAA06564 for ; Tue, 7 Apr 1998 07:51:51 -0700 (PDT) Received: from pau-amma.whistle.com(207.76.205.64) by whistle.com via smap (V1.3) id sma006560; Tue Apr 7 07:51:32 1998 Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id HAA27309 for hackers@FreeBSD.ORG; Tue, 7 Apr 1998 07:51:32 -0700 (PDT) (envelope-from dhw) Date: Tue, 7 Apr 1998 07:51:32 -0700 (PDT) From: David Wolfskill Message-Id: <199804071451.HAA27309@pau-amma.whistle.com> To: hackers@FreeBSD.ORG Subject: Re: Daylight Savings Time - bug Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 07 Apr 1998 03:01:05 -0700 >From: Studded >....There are a couple of us who are working on some >proposals for Paul Vixie along the following lines. >15 2S * * * /job > Would run the job in standard time all year round, ignoring DST >15 2U * * * /job > Runs the job in UTC time. > Without modification the job would happen or not happen the same way it >does now. Although it's a tad more verbose, my inclination would be to accomplish a similar objective by specifying a (complete) time zone designation (if this behavior is wanted -- of course, if it's not specified, the scheduling is for "local time"). Among other things, that would permit scheduling something for a certain time in (say) the MET time zone on a machine that happens to live in the US/Pacific (or US/Arizona!) time zone. I can imagine circumstances where that might be of value. However, the ability to always use "standard" (or "daylight savings") time for a given crontab entry would also be of value. >I would like to add a warning for the user if they schedule a >job that happens during the magic hour.... Yes, I think that would be a Good Thing. >3. cron saves the fact that it's warned the user about this job to the >file mentioned above, perhaps using an MD5 checksum of the job for >security? Not sure this is needed. Someone goes back into the crontab, if there's something in there worthy of note, crontab should probably mention it. It's not unheard of for an SA to set things up a certain way, then go on to a different position, and for the original SA's successor to have a bit to clean up.... :-) Maybe there could be an environment variable to tell crontab that the person in question doesn't want to hear its nattering.... You asked for comments...., david -- David Wolfskill dhw@whistle.com (650) 577-7158 pager: (650) 401-0168 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message