document that the port may not be immediately available for (re-)use

[tarun]

since getPort reserves a port and releases it to find an unused port number - trying to use that port number immediately afterwards may not work as *nix machines, which have a re-use timeout for the port to be available again.

This issue is for adding some documentation describing this behavior (if appropriate).

Related post:
https://unix.stackexchange.com/questions/17218/how-long-is-a-tcp-local-socket-address-that-has-been-bound-unavailable-after-clo

[tarun]

As per docs nodejs sets the option SO_REUSEADDR
https://nodejs.org/dist/latest-v8.x/docs/api/net.html#net_server_listen

[tarun]

A few more posts while I am debugging this on Ubuntu 14.04 Trusty and learning about BSD Socket Options SO_REUSEPORT and SO_REUSEADDR

https://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t
nodejs/node#2604 (comment)
http://man7.org/linux/man-pages/man7/socket.7.html

[tarun]

nevermind. I had a bug in my script - was starting the same server twice, instead of switching over and starting another item (was missing a git submodule argument).

The above doesn't seem to be a real issue since node always sets SO_REUSEADDR