[27569] in Hotline Meeting
w20-575-106
daemon@ATHENA.MIT.EDU (John Chase)
Mon Mar 27 07:18:07 1995
To: hotline@MIT.EDU
Date: Mon, 27 Mar 1995 07:18:02 EST
From: John Chase <jchase@MIT.EDU>
------- Forwarded Message
Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po8.MIT.EDU (5.61/4.7) id AA22941; Sun, 26 Mar 95 19:58:17 EST
Received: from SNOOPY.MIT.EDU by MIT.EDU with SMTP
id AA16392; Sun, 26 Mar 95 19:58:14 EST
From: cfields@MIT.EDU
Received: by snoopy.MIT.EDU (931110.SGI/4.7) id AA26334; Sun, 26 Mar 95 19:58:13 -0500
Date: Sun, 26 Mar 95 19:58:13 -0500
Message-Id: <9503270058.AA26334@snoopy.MIT.EDU>
To: jhawk@MIT.EDU
Cc: skunks@MIT.EDU, hotline@MIT.EDU, dkk@MIT.EDU
Subject: Re: New sgi failure mode??
> (If this kind of thing shouldn't go to skunks, please let me know).
bug-sgi I expect is appropriate. And hotline since who knew at the
time what the problem was. :-)
> I looked at it, examined /etc/athena/login/* and /usr/athena/lib/update/*,
> and everything seemed normal.
It is not normal for there to be a /usr/athena/lib/update yet.
It sounds like someone who thought they knew the implications of what
they were doing attached athena-77tom, which mounts over /usr/athena
Tom's old packs, and left the machine that way. This would cause a
certain amount of breakage. On reboot, a detach of everything gets
run, leaving no link at all sitting at /usr/athena.
The bug is that there is no /etc/athena/attach.conf yet preventing
users from doing this. The other bug is that track doesn't get run
automatically yet.
Craig
------- End of Forwarded Message
