Just after I sent out my update last week, our email server went belly up. As a
result I'm sure any responses to my email bounced. Thanks to those that did
attempt to reply and my apologies for the bounced mail. If those of you who
responded would be so kind and resend, I would greatly appreciate it. Now that
the mail is fixed, I'm back to this nfs issue.
The update and original post is listed below.
UPDATE:
I have shared the resource on the Sun to the world. The symptoms have not
changed. I have let the automounter create the /home1 directory for me and I
have created the directory myself. I have gone as far as giving the /home1 dir
777 permissions, changing the group name to the end users primary group before
the automounter takes over. I have given the same permissions on the Sun server.
Still no luck. I can define a system on the Sun -rw root=system, manually mount
the directory and browse the filesystem.
Its definately a permission issue. The automounter is doing its thing correctly.
The directory is always mounted when the user logs in but they don't have
permission to access it. Its very bizarre. The two systems that are working, I
can add new users and they work fine.
Whats different between the alpha workstations... nothing. They were all loaded
from the same image. I guess the bit fairy got a hold of the Sun station over
the holidays.
Origional post:
I have a Sun Ultra 60 Raid 5 server running 2.6 that we are testing as a $HOME
server for Compaq XP1000 workstations running Tru64 Version 4.0F. On the Sun we
have simply shared the appropriate filesystem with an option of
rw=system:system:system etc. The Compaq's automount the home directory when the
user logs in.
I singled out a few compaq workstations to test this with and it has been
working fine. Today I propogated those changes to the rest of the clients. Now
that I have done that, the remaining clients fail to mount the users home
directory. Well, not exactly. Using "df" before and after the attempted login
will show you the automounter did indeed make the mount however the user does
not have permission to read the data. The user is logged in with a temp home of
/. (Keep in the mind the select machines we used for testing, which are
identical to every other machine, still work ok).
A little investigation shows that if I add the end user to the "system" group on
the Compaq, the user has no problems logging in and seeing all their files. The
same user is not in the system group on the select machines used for testing.
I've checked UID's, GID,s permissions, connectivity... Any thoughts would be
appreciated.
Mark S. Yamnicky
Boeing Satellite Systems
marco_at_nirvana.es.hac.com
310.364.6473
Received on Thu Jan 04 2001 - 05:24:40 NZDT