[25445] in Athena Bugs
update_ws should log more stuff to update.log
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Wed Jan 14 17:49:53 2004
Mime-Version: 1.0
Message-Id: <p05230101bc2b76629de1@[0.0.0.0]>
Date: Wed, 14 Jan 2004 17:50:11 -0500
To: bugs@mit.edu
From: Jonathan Reed <jdreed@mit.edu>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Errors-To: bugs-bounces@mit.edu
This is a cross between a bug and a feature request, but Jonathon
suggested I send it here. In attempting to figure out why an Ultra5
wasn't updating to 9.2, I poked at it with athinfo - update.log
showed nothing interesting (in fact, nothing since the 9.1.27
update). A df query revealed that it had the old partition scheme of
/, /usr, /var, and from that, I guessed that it was failing to take
9.2 because of that. Jonathon later mentioned that the syslogs
stated that in fact that's why the machine had failed.
However the syslogs are not accessible remotely (at least not to mere
mortals). Update.log is accessible via athinfo. It would make sense
if an update fails for reasons of space, that in addition to logging
it in the syslogs, it gets logged to update.log, too. Admittedly, if
run interactively, update_ws will explicitly tell you that there's no
space, but there are times when a user who is calling can't run it
for whatever reason, so it'd be nice to have that info in update.log
-Jon
--
-------------------
Jonathan Reed
jdreed@mit.edu
-------------------
