From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9205 invoked by alias); 20 Jan 2003 19:19:58 -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 9133 invoked from network); 20 Jan 2003 19:19:58 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 20 Jan 2003 19:19:58 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 18FDE3EFD; Mon, 20 Jan 2003 14:20:00 -0500 (EST) Message-ID: <3E2C4BDF.9020900@redhat.com> Date: Mon, 20 Jan 2003 19:19: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: Phil Edwards Cc: overseers@sources.redhat.com Subject: Re: NTP, and gccadmin's crontab about to be activated References: <20030120012647.A22573@disaster.jaj.com> <3E2C4798.7040100@redhat.com> <20030120190446.GA3122@disaster.jaj.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00151.txt.bz2 >> To the contrary. It will cause GDB and GCC's jobs to fight with each >> other! Just add 8 to all the crontab times and that way GCC ontinues >> to run at that same old time. > > > The only thing that GCC's crontab is doing is the nightly version bump. > Shouldn't affect GDB at all. Yes, that definitly won't affect GDB. In fact, like GDB, you should run it hourly. That way, if the machine is down for a few hours, it fixes itself. Andrew