[1335] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #124: De-crustify the CellServDB

daemon@ATHENA.MIT.EDU (Evan Broder)
Fri Mar 6 19:09:12 2009

Message-ID: <49B1B9B3.1090305@mit.edu>
Date: Fri, 06 Mar 2009 19:02:59 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Tom Fitzgerald <tfitz@mit.edu>
CC: Jonathon Weiss <jweiss@mit.edu>, debathena@mit.edu
In-Reply-To: <1236383357.5851.98.camel@sligo.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Tom Fitzgerald wrote:
> But there's no reason to have CellServDB entries for cells that
> *do* have AFSDB records - they'll be handled correctly.
>   

Yes. That's roughly my point.

> The CellServDB needs to contain cells that don't have AFSDB
> records, if anyone might care about them.
>   

I'm not suggesting we (or g.c.o) should remove cells that are still
online and don't have AFSDB records.

> And I still don't think anybody here is in a position to decide
> what cells are closely related to MIT.  Any Athena user in any
> department may feel that some random cell is closely related to
> MIT because it has data he cares about.  If that cell lacks
> AFSDB records and isn't in Athena's CellServDB then he is going
> to be stuck troubleshooting something he should not need to.
>   

In terms of "closely related to MIT", I basically mean "cells whose name
ends with mit.edu", as a failsafe in case of DNS apocalypse.

- Evan

home help back first fref pref prev next nref lref last post