Hi,
during boot we mount some fs via NFS on our local NFS-server. The remote
NFS-server is far away and the connection sometimes hangs. To avoid the
local NFS server hanging too long, waiting for the remote NFS, we mount
in background with
mount -at nfs,nfs4 & sleep 8
Now it happens that when the remote NFS server is a bit slow, our local
NFS server can't start:
May 25 12:25:48 backus rpc.mountd: Could not bind name to socket: Address already in use
That's because we define MOUNTD_PORT=700 due to some firewall reasons.
But port 700 is still blocked by some mount process:
backus /root# netstat -a -n |grep 700
tcp 0 0 <local nfs server ip:700 <remote nfs server ip>:735 TIME_WAIT
We mount about 30 directories from the remote server and the local server
seems to use a bunch of ports initially.
Can I avoid the "mount" process using port 700? Like telling it to use only
port > 700 etc.?
This is SLES 10 btw, kernel 2.6.16.
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs