Esteemed Colleagues:
An NFS mount from my 9.3-RELEASE-p49 server, on which Port 2049 has been opened, hangs, and then times out, unsuccessfully. This is the /etc/exports file:
When the V4 line is commented out, the mount fails immediately, indicating that port 2049 is indeed open. Moreover, when the V4 line is changed, and /home/jay/.elm is replaced by / (i.e., the root directory), the mount succeeds immediately. But then the client can mount anything, so that is, of course, an unacceptable solution; I want the client to be able to mount only the /home/jay/.elm directory (apparently the 2nd line is ignored for NFSv4 mounts, because when the first line is the root directory, the client can mount anything). When the client is localhost, then the mount succeeds immediately, but that is probably because it is downgrading to NFSv3 and accessing mountd and nfsd as RPC services, which is, of course, impossible when the server is firewalled, because you cannot know what ports to open.
Please resist the temptation to give me the facile answer "don't run 9.3-RELEASE on your server" and to say nothing more; upgrading the server is not an option at present. Also, I am, of course, cycling all daemons whenever I change /etc/exports, so you need not tell me to do that. Also, there are no symbolic links leading up to /home/jay/.elm, so you need not tell me to check for that.
Thank you in advance for any and all replies.
jay at m5 dot chicago dot il dot us
An NFS mount from my 9.3-RELEASE-p49 server, on which Port 2049 has been opened, hangs, and then times out, unsuccessfully. This is the /etc/exports file:
Code:
V4: /home/jay/.elm
/home/jay/.elm -ro -mapall=nobody
When the V4 line is commented out, the mount fails immediately, indicating that port 2049 is indeed open. Moreover, when the V4 line is changed, and /home/jay/.elm is replaced by / (i.e., the root directory), the mount succeeds immediately. But then the client can mount anything, so that is, of course, an unacceptable solution; I want the client to be able to mount only the /home/jay/.elm directory (apparently the 2nd line is ignored for NFSv4 mounts, because when the first line is the root directory, the client can mount anything). When the client is localhost, then the mount succeeds immediately, but that is probably because it is downgrading to NFSv3 and accessing mountd and nfsd as RPC services, which is, of course, impossible when the server is firewalled, because you cannot know what ports to open.
Please resist the temptation to give me the facile answer "don't run 9.3-RELEASE on your server" and to say nothing more; upgrading the server is not an option at present. Also, I am, of course, cycling all daemons whenever I change /etc/exports, so you need not tell me to do that. Also, there are no symbolic links leading up to /home/jay/.elm, so you need not tell me to check for that.
Thank you in advance for any and all replies.
jay at m5 dot chicago dot il dot us