hm interesting question. I tried locally out of curiosity and it seems to work. /mnt/chris is NFS # sudo mount --bind /home/chris/test-files/ /mnt/chris/tmp/ # mount | grep chris //172.24.1.10/chris on /mnt/chris type cifs /dev/nvme0n1p4 on /mnt/chris/tmp type ext4 # cd /mnt/chris/tmp/ now shows the local files. Unsure how permissions/gid/uid would work in this case though. Do you get the CIFS-enforced ones or the mounted directory ones? Mine matched before the mount. On Tue, Mar 23, 2021, at 12:02 PM, Robert P. J. Day wrote: > > friend setting up an NFS mount to share some python scripts was > explaining to me that these scripts are set up in such a way that they > expect, on the NFS client, to find their client-specific R/W data > directories somewhere *below* (that is, within) the NFS mount. > > i kind of cringed at that, and suggested it would be way easier to > simply pass the script(s) a single environment variable defining where > the data was to be found, but apparently that will require some major > rewriting. > > is there a simple way to mount a local directory somewhere below an > NFS mount point on the client? i haven't messed with NFS for a while > so i've forgotten pretty much everything i ever knew about it. can one > create a symlink to a directory outside of the NFS mount so that all > clients have their own data directory? > > or perhaps a bind mount, or something similar? thoughts? > > rday > > > To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org > To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org > To visit the archives: https://lists.linux-ottawa.org > > To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org To visit the archives: https://lists.linux-ottawa.org