From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17137 invoked by alias); 20 Jan 2003 19:49:27 -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 17112 invoked from network); 20 Jan 2003 19:49:26 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 20 Jan 2003 19:49:26 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 8EB953EFD; Mon, 20 Jan 2003 14:49:28 -0500 (EST) Message-ID: <3E2C52C8.7020306@redhat.com> Date: Mon, 20 Jan 2003 19:49:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Joseph S. Myers" Cc: Phil Edwards , overseers@sources.redhat.com Subject: Re: NTP, and gccadmin's crontab about to be activated References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00152.txt.bz2 > On Mon, 20 Jan 2003, Phil Edwards wrote: > > >> The only thing that GCC's crontab is doing is the nightly version bump. >> Shouldn't affect GDB at all. > > > And update_web_docs, but that should be much faster on the new machine, > and be finished long before GDB's crontab starts. The current schedule was carefully arranged and for good a reason. It balanced the system load. GCC's task (the longest running and heavest) at the time when the system had the lightest load (the middle of the apec day when europe and america were in bed). Now is not the time to review that schedule. Rather, the schedule should be reviewed in a few weeks when the system has settled and we've hard data on how long each job is taking. Hopefully, at that time, it will be possible to do things like move GDB's start time out so that it isn't so close to that peak 1am (5pm US pacific) time slot. The last thing people should be considering is trying to schedule things at 00:00 gmt and, consequently, totally overload that period. Andrew