On 12/01/2014 07:02, Daniel Corbe wrote:
Generally the answer to your question is no. Two applications cannot
occupy the same port on the same protocol at the same time.
To expand on this answer and to hopefully shed some light on why the
behavior you're observing with your application is absolutely correct;
the calling application (in this case, nc) has to explicitly call bind(2)
before it can begin accepting connections. If that port is already in
use then the call to bind(2) will fail. And in your case I suspect nc
is simply choosing to silently fail.
Here the question is what does it mean "occupy the port"? The first
instance isn't listening any more. The listening socket was closed. Why
the presence of the socket that was accepted from (now closed) listening
socket in the first instance is considered "occupying it"?
Actually no system call in the second instance ever fails.
Yuri
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
