[45487] in SIPB bug reports
Re: Report on your nightly job (sipbsrc FILES rebuild)
daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Fri Dec 28 17:03:14 2012
From kaduk@MIT.EDU Fri Dec 28 22:03:13 2012
Return-Path: <kaduk@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.mit.edu
Received: (qmail 21055 invoked from network); 28 Dec 2012 22:03:13 -0000
Received: from mailhub-auth-4.mit.edu (18.7.62.39)
by charon.mit.edu with SMTP; 28 Dec 2012 22:03:13 -0000
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id qBSM37ld015706;
Fri, 28 Dec 2012 17:03:07 -0500
Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37])
(authenticated bits=56)
(User authenticated as kaduk@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id qBSM3400010982
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 28 Dec 2012 17:03:06 -0500 (EST)
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308)
id qBSM34Pw007668; Fri, 28 Dec 2012 17:03:04 -0500 (EST)
Date: Fri, 28 Dec 2012 17:03:04 -0500 (EST)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: John Hawkinson <jhawk@MIT.EDU>
cc: rtfm-maintainers@MIT.EDU, bug-sipb@MIT.EDU
Subject: Re: Report on your nightly job (sipbsrc FILES rebuild)
In-Reply-To: <20121228215106.GM1620@ringworld.MIT.EDU>
Message-ID: <alpine.GSO.1.10.1212281655220.12170@multics.mit.edu>
References: <20121228215106.GM1620@ringworld.MIT.EDU>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Fri, 28 Dec 2012, John Hawkinson wrote:
> Benjamin Kaduk <kaduk@MIT.EDU> wrote on Fri, 28 Dec 2012
> at 13:48:26 -0500 in <alpine.GSO.1.10.1212281345030.12170@multics.mit.edu>:
>
>> Is anyone looking into this? It seems quite poor for an automated
>
> This seems a bit disingenuous, since you knew from zephyr
> conversations on -c sipb that I had this on my slow queue (and how I
Those same zephyr conversations where you indicated that you would prefer
someone else to deal with it?
Anyway, rtfm-maintainers is not a subset of bug-sipb, and due to the
peculiarities of the mail path, I could not even be sure that it was being
seen as bug-sipb by all recipients. A concrete email asking for status
seemed prudent, and perhaps even likely to trigger that "someone else" to
do something.
> was discinclined to deal with it promptly because of
> harassment). Anyhow...
You never replied to my question regarding what actions would be useful to
take to hasten resolution of the issue as opposed to inciting delays.
> Alex Rolfe <arolfe@MIT.EDU> wrote on Fri, 28 Dec 2012
> at 14:34:59 -0500 in <ubzbodeotr0.fsf@dr-wily.mit.edu>:
>
>> The cronjob regenerated /afs/sipb.mit.edu/project/sipbsrc/FILES and
>
> Looks like you disabled it this afternoon...
I worry that this merely masks a reminder of other potential issues with
the services run on the machine.
-Ben
