Han Boetes wrote: > Alexander Hall wrote: >> The problem is that nfs shares does not traverse file system >> mount points once initialized. Since nfs probably was started >> prior to mounting the msdos partition (with the noauto option in >> /etc/fstab), nfs would only share the contents of the mount >> point directory itself. >> >> A ``pkill -HUP mountd'' might help after mounting the msdos file >> system, in order to make mountd aware of the new file system >> "overriding" the mount point directory. > > I'm sorry, it doesn't work like you expect.
I stand corrected at this point. The file system to share is not ultimately determined at the time of mountd start up or (re-)configuration. However, it seems to be determined at the time of the nfs mount, so if the mount was performed prior to mounting the msdos file system, the client would only have access to the "parent" file system. I could not read from your earlier posts if this was the case. Some minor testing seem to indicate that the ``kill -HUP'' makes no difference at all unless the exports file has been changed. > On the OpenBSD server: > > ~% grep usb /etc/fstab > /dev/sd0i /mnt/usb msdos rw,nodev,nosuid,noauto,noexec 0 0 > ~% grep usb /etc/exports > /mnt/usb -maproot=han:nfs marsupilami > ~% mount |grep usb > /dev/sd0i on /mnt/usb type msdos (NFS exported, local, uid=1000, gid=0) > ~% sudo pkill -HUP mountd > ~% ls /mnt/usb > foofile > > On the linux client: > > ~% mount G /mnt/usb > haddock:/mnt/usb on /mnt/usb type nfs (rw,addr=172.16.11.1) > ~% ls /mnt/usb I am not sure here either which mount (nfs vs msdos) was performed first. /Alexander
