[Beowulf] automount on high ports
Robert G. Brown
rgb at phy.duke.edu
Wed Jul 2 08:12:05 PDT 2008
On Wed, 2 Jul 2008, Carsten Aulbert wrote:
> Which corresponds exactly to the maximum achievable mounts of 358 right
> now. Besides, I'm far from being an expert on TCP/IP, but is it possible
> for a local process to bind to a port which is already in use but to
> another host? I don't think so, but may be wrong.
AFAIK, no they don't. The way TCP daemons that listen on a
well-known/privileged port work is that they accept a connection on that
port, then fork a connection on a higher unprivileged (>1023) port on
both ends so that the daemon can listen once again. You can see this by
running e.g. netstat -a. Many daemons have a limit that can be set on
the number of simultaneous connections they can manage.
However, this is for TCP ports that maintain a persistent connection.
UDP ports are "connectionless" and hence somewhat different. They tend
to make a connection, receive a command/request for some service,
immediately deliver the result, and end the connection. NFS used to be
built on top of UDP, and honestly I don't know what it does and how it
(NFSv3) does it on TCP and am too lazy to look it up, but the RFCs are
there to be read.
> Beowulf mailing list, Beowulf at beowulf.org
> To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
Robert G. Brown Phone(cell): 1-919-280-8443
Duke University Physics Dept, Box 90305
Durham, N.C. 27708-0305
Book of Lilith Website: http://www.phy.duke.edu/~rgb/Lilith/Lilith.php
Lulu Bookstore: http://stores.lulu.com/store.php?fAcctID=877977
More information about the Beowulf