[24046] in Athena Bugs
Re: sun4 9.2.16: gnome
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Sep 11 18:37:21 2003
From: Greg Hudson <ghudson@MIT.EDU>
To: Bill Cattey <wdc@mit.edu>
Cc: Alex T Prengel <alexp@mit.edu>, bugs@mit.edu
In-Reply-To: <200309112042.h8BKgpen021562@tokata.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1063319838.20507.219.camel@error-messages.mit.edu>
Mime-Version: 1.0
Date: Thu, 11 Sep 2003 18:37:18 -0400
On Thu, 2003-09-11 at 16:42, Bill Cattey wrote:
> What can be done about the other systems that have not properly
> run athchanges?
Well, they'll run athchanges at the next update, but we probably want to
do better than that. Fortunately, most of the systems installed
recently for renewal were done just before the switchover last
Wednesday; using athinfo, I found only eight affected machines:
barker-6-5, dit, joust, m38-370-10, mull, prsns1, spy-hunter, stage8
Logging in as root and running /srvd/install/athchanges should fix the
machines.
> How can users who are now having problems be put to rights?
I'm not 100% sure about this yet, since the first remedy I suggested to
Alex didn't seem to work.
Alex, assuming you moved aside the .gconf and .gnome2 directories as I
suggested in my last piece of mail, can you tar up the moved-aside
directories and put the tarfiles somewhere I can get at them?
> How can we detect this sort of thing in the future via testing rather
> than with a deployment of broken systems?
When we test an install, we should try a login with a test account. We
can't catch all problems without a laborious amount of testing, but we
can catch the really visible ones.
