This may not be the correct forum, but it may be a place to start.

I am using and old Celeron box running RH 9 as a Samba and NFS file
server.  Beyond the "normal" mountings I have the follwing:
/dev/hdc1       /storage
/dev/hdg1       /storage/files
/dev/hdh1       /storage/files/Unsorted

hdc is a small drive (40gig) the other two are larger (120gig)

my exports contains

/storage/files *(rw)

I forget what the samba conf files has exactly, but /storage/files is
one of the published drives.  I'm away from my network so I can't check


The problem is this:  When I mount the directory from windows using
samba, I can see into the directory and see all of the enclosed files
and directories.

When I mount the NFS share, both from UnixForWindows or another Fedora
box, I can see the directory, but not the files within it.  The
directory appears to be empty.

IS this a feature rather than a bug?  Is this the way NFS is intened to
work or do I have something set incorrectly.

The files and directories all have identical privs.

Thanks in Advance

ARS

[ Post a follow-up to this message ]

On Fri, 4 Feb 2005 17:24:50 -0600, a posting issued forth from ARS...
> This may not be the correct forum, but it may be a place to start.
>
> I am using and old Celeron box running RH 9 as a Samba and NFS file
> server.  Beyond the "normal" mountings I have the follwing:
> /dev/hdc1       /storage
> /dev/hdg1       /storage/files
> /dev/hdh1       /storage/files/Unsorted
>
> hdc is a small drive (40gig) the other two are larger (120gig)
>
> my exports contains
>
> /storage/files *(rw)
>
> I forget what the samba conf files has exactly, but /storage/files is
> one of the published drives.  I'm away from my network so I can't check
>
>
> The problem is this:  When I mount the directory from windows using
> samba, I can see into the directory and see all of the enclosed files
> and directories.
>
> When I mount the NFS share, both from UnixForWindows or another Fedora
> box, I can see the directory, but not the files within it.  The
> directory appears to be empty.
>
> IS this a feature rather than a bug?  Is this the way NFS is intened to
> work or do I have something set incorrectly.
>

Feature. NFS exports don't traverse mount points. Don't know the
historical reason, but it's the way it is.

--
Jacob
mailto:`echo wnpbo@urvqre.ubzryvahk.arg | tr [a-z] [n-za-m]`

[ Post a follow-up to this message ]

Jacob <Jacob@FAKEDOMAIN.NOTHERE> wrote:
 
>
> Feature. NFS exports don't traverse mount points. Don't know the
> historical reason, but it's the way it is.

That's what I had guessed.

Thanks for the quick response...  I assume NFS will have the same
restriction IRT links, both soft and hard?

ARS

[ Post a follow-up to this message ]

On Sat, 5 Feb 2005 11:07:45 -0600, a posting issued forth from ARS...
> Jacob <Jacob@FAKEDOMAIN.NOTHERE> wrote:
> 
>
> That's what I had guessed.
>
> Thanks for the quick response...  I assume NFS will have the same
> restriction IRT links, both soft and hard?
>

Not sure exactly what you're asking. You can't make a hard link to a
file that lives on a different partition. If it's just something on the
same partition, but no under the export, then it will be seen as the
regular file, as hard links always are.

As for symlinks, it looks like, from the tests I've done, that they're
evaluated as absolute links, then compared with the filesystem on the
client computer. The only way to expose the files you want, is to export
and mount all the filesystems in question.

GL
--
Jacob
mailto:`echo wnpbo@urvqre.ubzryvahk.arg | tr [a-z] [n-za-m]`

[ Post a follow-up to this message ]