From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2977 invoked by alias); 17 Jan 2003 16:08:28 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 2924 invoked from network); 17 Jan 2003 16:08:25 -0000 Received: from unknown (HELO redhat.com) (66.30.22.225) by sources.redhat.com with SMTP; 17 Jan 2003 16:08:25 -0000 Received: by redhat.com (Postfix, from userid 201) id 8061B1BD63; Fri, 17 Jan 2003 11:09:31 -0500 (EST) Date: Fri, 17 Jan 2003 16:08:00 -0000 From: Christopher Faylor To: Alexandre Oliva Cc: "Joseph S. Myers" , overseers@sources.redhat.com Subject: Re: sources.redhat.com downtime Message-ID: <20030117160931.GF4335@redhat.com> Mail-Followup-To: Alexandre Oliva , "Joseph S. Myers" , overseers@sources.redhat.com References: <3E273C8E.8030203@redhat.com> <20030117153716.GB4335@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-q1/txt/msg00085.txt.bz2 On Fri, Jan 17, 2003 at 01:59:19PM -0200, Alexandre Oliva wrote: >On Jan 17, 2003, Christopher Faylor wrote: >> Does anyone have a "move crontab to a new timezone" script, maybe? > >There's always the option of running crond with the Pacific timezone, >to give maintainers more time to prepare to the switch-over. I thought of that but that sort of eliminates the whole reason for the switch. I'll probably have lots of time during tomorrow's rsync to adjust everything if no one can point me to an automated way of doing this. I can even make the new system available during the switch if people want to logon and fix their crontab entries. cgf