From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13396 invoked by alias); 12 Aug 2014 15:53:59 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 13384 invoked by uid 89); 12 Aug 2014 15:53:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 12 Aug 2014 15:53:57 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7CFruZI027534 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 12 Aug 2014 11:53:56 -0400 Received: from [10.3.113.59] (ovpn-113-59.phx2.redhat.com [10.3.113.59]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s7CFrtEc006170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 12 Aug 2014 11:53:55 -0400 Message-ID: <53EA3898.5090100@redhat.com> Date: Tue, 12 Aug 2014 15:53:00 -0000 From: Yaakov Selkowitz User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: overseers@sourceware.org Subject: Re: Cygwin infrastructure assistance, part 3 References: <53E9A5DA.1090100@redhat.com> In-Reply-To: <53E9A5DA.1090100@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2014-q3/txt/msg00091.txt.bz2 On 2014-08-12 00:27, Yaakov Selkowitz wrote: > It appears that the same jobs (upset and check-cygwin-mirrors) are being > run from both the cygwin@ and cygwin-admin@ crontabs simultaneously, > which is causing some conflicts. I am fairly sure that they were only > in the latter when I started, and in any case I only have access to the > latter. Could someone please check these and make sure that only the > cygwin-admin@ crontab has these? There may also be jobs in the root crontab that are Cygwin related. Could someone please check this as well; we want all Cygwin-specific jobs in the cygwin-admin@ crontab so that we can manage them ourselves. TIA, -- Yaakov Selkowitz Associate Software Engineer, ARM Red Hat, Inc.