Everyone knows the classic model of a process listening for connections on a socket and forking a new process to handle each new connection. Normal practice is for the parent process to immediately call close on the newly created socket, decrementing the handle count so that only the child has a handle to the new socket.
I’ve read that the only difference between a process and a thread in Linux is that threads share the same memory. In this case I’m assuming spawning a new thread to handle a new connection also duplicates file descriptors and would also require the ‘parent’ thread to close it’s copy of the socket?
No. Threads share the same memory, so they share the same variables. If you close socket in parent thread, it will be also closed in child thread.
EDIT:
man fork: The child inherits copies of the parent’s set of open file descriptors.
man pthreads: threads share a range of other attributes (i.e., these attributes are process-wide rather than per-thread): […] open file descriptors
And some code:
Output is: