Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SO_REUSEPORT option. How a child process gets its own listening socket? #859

Open
creamsodainyourmouth opened this issue Dec 23, 2022 · 1 comment

Comments

@creamsodainyourmouth
Copy link

Hi!)
I have a similar question, discussed here:
#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?

@walkor
Copy link
Owner

walkor commented Dec 25, 2022

When SO_REUSEPORT is true master will not create listening sockets, but each children process will create it's own listening socket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants