From owner-freebsd-hackers Mon Dec 20 0:43:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id 365AD15100 for ; Mon, 20 Dec 1999 00:43:12 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id JAA08086; Mon, 20 Dec 1999 09:43:10 +0100 (CET) (envelope-from bd) To: freebsd-hackers@freebsd.org Subject: UTC time in crontabs From: Bjorn Danielsson Date: 20 Dec 1999 09:43:10 +0100 Message-ID: Lines: 16 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have made a small patch (about 10 lines of code) to "cron" that lets people choose between localtime and gmtime for their crontab entries. The choice is made depending on the setting of an environment variable in the crontab file. The cost is a factor 2 for the tiny amount of work that cron does when it checks all the crontab entries every minute. Any interest in this? I finally got tired of having to use local daylight saving time for crontabs after seeing my nightly statistics-gathering scripts having to deal with 23 hour days, 25 hour days, some scripts running twice the same night, or not running at all, etc. -- Björn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message