[2317] in athena10
Re: [Debathena] #208: graphical login doesn't deal well with being
daemon@ATHENA.MIT.EDU (Debathena Trac)
Thu Apr 16 23:09:58 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: geofft@mit.edu, mitchb@mit.edu
Date: Fri, 17 Apr 2009 03:09:40 -0000
Reply-To:
Message-ID: <052.e4e966beb31620666d4dd7fbd770ef7d@mit.edu>
In-Reply-To: <043.da6f47b1b14e683c2885a48ad4e96517@mit.edu>
Content-Transfer-Encoding: 8bit
#208: graphical login doesn't deal well with being unplugged-------------------+--------------------------------------------------------
Reporter: geofft | Owner:
Type: defect | Status: new
Priority: major | Component: --
Keywords: |
-------------------+--------------------------------------------------------
Comment(by mitchb):
AFS will not remain 'sad until "fs checks" is run'. The cache manager
will periodically poll servers it thinks are down (by default, every
three minutes). You can run 'fs checks' if you don't want to wait for
that. Basically, my reply to Adam was getting at the point that "it
won't work immediately, and this isn't a change, if it was disconnected
for a while; you can reboot if you don't want to wait".
But certainly agreed that a diagnostic error would be a good idea. On
Athena 9, there was a "bad" diagnostic error - "Workstation failed to
activate successfully" or something like that generally meant that
something was wrong with net. Or "no clusterinfo for ____(hostname you
know has clusterinfo)".
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/208#comment:1>Debathena <http://debathena.mit.edu/>MIT Debathena Project
