SO_REUSEPORT option. How a child process gets its own listening socket?
Open
- Dominant language
- PHP
- Stars
- 11.6k
- Forks
- 2.2k
- Avg merge
- 11h 30m
- Merged PRs (30d)
- 3
Description
Hi!)
I have a similar question, discussed here:
https://github.com/walkor/Workerman/issues/156
I would like to understand how child process get it own listening socket. Master creates several listening sockets and then fork, after this each of workers inherits several sockets, and should close (decrease ref counter) all except one socket, and accept new connection from it? As a result all workers have independent queue for receiving request to connection?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.