On Sun, 2019-12-08 at 13:25 -0500, Bob Goodwin wrote:
On 2019-12-08 12:42, Patrick O'Callaghan wrote:
> On Sun, 2019-12-08 at 11:35 -0500, Bob Goodwin wrote:
> > I guess you mean exports?
> >
> > [root@NFS-Server bobg]# cat /etc/exports
> > # /nfs4exports/home
> > 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check)
> Is that the actual file? If so, why is there a '#' at the start of the
> first line, and why is it split into two lines (unless that's an
> artefact of your email client)?
.
Why the #'s. to comment out the lines and limit it to just whatever was
uncommitted that I was trying at tat time. just a random collection of
things tried ...
It's not really practical to debug what's going on unless you show what
is actually in the /etc/exports file when you get the failure.
And it's *very* important to show it as it really is, without any line
breaks introduced by your mailer.
> This is my file:
> $ cat /etc/exports
> /home/Media 192.168.0.0/16(ro,all_squash,insecure)
> /home/poc/Stuff 192.168.122.0/24(rw)
>
> poc
.
The "/home/Media" part is what I need for my /etc/exports file, where,
how, do I find that? Perhaps /home/bobg/Public? none of that matters if
NFS does not run which is what I am seeing ...
You don't "find" it. It's the server directory you want to access from
the client(s). That just happens to be one I use. It could in principle
be any directory that exists on the server.
poc