[16914] in Athena Bugs
Re: Attach errors in Athena 8.3
daemon@ATHENA.MIT.EDU (Dan Winship)
Wed Jun 23 12:41:00 1999
Date: Wed, 23 Jun 1999 12:40:53 -0400 (EDT)
Message-Id: <199906231640.MAA92845@antharia.mit.edu>
From: Dan Winship <danw@MIT.EDU>
To: "Thomas H. Grayson" <thg@MIT.EDU>
Cc: bugs@MIT.EDU, karen@MIT.EDU, phils@MIT.EDU
In-Reply-To: <199906231459.KAA16918@aalto.mit.edu>
> The Athena 8.3 version of 'attach' does some strange things on login.
> When I login, I see these messages four times:
>
> Badly formatted entry in /var/athena/attachtab
> Operation aborted
This error message only occurs in the pre-8.3 version of attach. From
looking at your .environment, it looks like the problem is that you're
running the attach from the fixes locker, which won't work on an 8.3
machine, since the attachtab format is completely different. You need
to run the normal attach under 8.3.
> When I login via telnet (but not at the console), I also see this:
>
> Warning: Attach failed; you have no home directory
>
> aalto.mit.edu (SunOS release 5.6 Generic_105181-13) (pts/0)
We saw this behavior on test.dialup when we first upgraded it to 8.3,
and later determined that it was because we were running a telnetd
built from the 8.2 source tree. Do you have your own custom telnetd on
that machine?
> I should note that I have aliased 'attach' to
> 'attach -o rsize=8192,wsize=8192'. I had been told some time ago
> that the 8.3 version of attach would support these options on NFS
> attaches. We've been using a version in the 'fixes' locker that
> does this for Athena 8.2. However, these options are still being
> ignored.
Hm... they're not actually being ignored, they're just being
malformatted:
danw@antharia:~> attach -o rsize=8192,wsize=8192 crlbin
attach: GROTTO.MIT.EDU:/u5/crlbin attached to /mit/crlbin for filesystem crlbin
danw@antharia:~> mount | grep crlbin
GROTTO.MIT.EDU:/u5/crlbin on /mit/crlbin type nfs (vers=3,wsize=1024,soft,ro,rsize=8192,wsize=8192nosuid,nodev,dev=100002)
(The "wsize=8192" seems to have gotten squished together with the
"nosuid".)
I'll submit a patch for that and it should be fixed in the next patch
release.
-- Dan
