SUMMARY: NFS oddity (for me at least)

2007-12-25 5:30:00

The problem was with the hostname. For some reason, it wanted the FQDN
instead of the short name. Once I put that in, it worked like a charm.

Thanks to everyone that helped (and those nice enough to tell me they were
out of the office having a good time).

Mike Newton [jmnewton at duke.edu]
John Birtley [john at nemean.com]
Stan.Pietkiewicz at statcan.ca
Chris Ruhnke [ruhnke at us.ibm.com]
Horton, William M \(I75\) [I75 at bechteljacobs.org]
Andrew Williams [snowman at ican.net]

---------------------------------------------------------
Gary Paveza, Jr.
Senior Systems Administrator - HP-UX CSE
(302) 252-4831 - phone

-----Original Message-----
From: codeprof-bounces at codeprof.com
[mailto:codeprof-bounces at codeprof.com] On Behalf Of Paveza, Gary
Sent: Wednesday, October 26, 2005 10:11 AM
To: 'codeprof at codeprof.com'
Subject: NFS oddity (for me at least)

I'm trying to export an NFS share with read/write permissions to just one
host.

On the NFS server, if I use the line:

share -F nfs -o rw=<hostname> <share>

where hostname is the name of the NFS client which will automount the
filesystem (using the automountd daemon) and <share> is the directory to be
shared.

This results in a access denied when I try to access this directory on the
client

If I change the NFS server entry to :

share -F nfs -o rw <share>

It works just fine (of course, everyone can mount it then)

Using Solaris 9 for both server and client. Any ideas?

---------------------------------------------------------
Gary Paveza, Jr.
Senior Systems Administrator - HP-UX CSE
(302) 252-4831 - phone
_______________________________________________
codeprof mailing list
codeprof at codeprof.com
http://www.codeprof.com/execute/ask/?codeinfoid=38229

Comments

Got something to say?

You must be logged in to post a comment.