[KLUG Members] NFS and time travel

[Robert G. Brown]

On Sun, 28 Dec 2003 17:19:32 -0500, Bruce Smith <bruce@armintl.com> wrote:

>> >>The results are no different if I use IP addresses now.
>> >Try IP's anyway, if you haven't.  
>> I have, whch is why I wrote what I did. I'm reporting, not speculating.
>And I'm making absolutely sure.   :-)
As am I, for clarity.

>I guess the next thing I'd try is trial & error with different options
>(on mount and in exports).
Yes, I referred to this in my last message.

>And, since this is for your internal network, why are you specifying
>hostnames or IP's at all?
Well, for one thing, you never know when someone's going to come over
to this place and want a connection. I also don't want to export to my
own firewalls, which might not have nfs now in any case, but it seems
like a good precaution.

The other reason is that I'm going to be setting up NFS for a client 
or two, so exploring more options is better.

Finally, it's an additional hedge against making some really serious 
mistakes. Suppose there are two hosts that have exported /usr, as an
example.... you wouldn't want to mount the wrong one, so on one:

/usr	hosta(ro) hostb(ro) hostd(ro)

and on another....

/usr	hostc(ro) hoste(ro) hostq(ro)

which stops those clients from playing "mix n'match" with stuff like 
that.

Why not export them to the world?  (try it!)
I'll try it, I'll try it. It probably won't make it into any of the 
final exports, but what the heck.

>At least I hope this is only for your internal network only.
Lord yes, see above!

>You should know that NFS stands for:  "No File Security".   ;-)
Yes, purely internal.

>> >I've had weird problems that's solved before - to the point I _always_
>> >use IP addresses in /etc/exports now.  (and "permission denied" is
>> >almost always a /etc/exports problem)
>> It looks like some odd problem with DNS, maybe reverse lookups or
>> something [??].
>Could be.  It's been too long to remember.  I got in the habit of using
>IP's a LONG time ago.
I'm going to re-examine stuff like the reverse lookup defs in the internal
DNS server. If I left something out, or if the network has changed, that 
may be the problem...

>> >Other things to watch out for: 
>> Nice to have this checklist, for general reference...
>The only other thing I can thing of (for general reference) is nested
>exports.  I've seen people make the mistake of exporting both:
>"/a/b/c/d/e"   -and-   "/a/b/c"   Which causes problems.  
>Only the second export is needed to mount either.
Right, that's a nice one. People who can't think in these terms need not
apply.

Later on I'll post what worked and what didn't on those mounts...

							Regards,
							---> RGB <---