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

Accept a FD instead of a port number. #37

Open
noteed opened this issue Jun 25, 2013 · 6 comments
Open

Accept a FD instead of a port number. #37

noteed opened this issue Jun 25, 2013 · 6 comments

Comments

@noteed
Copy link

noteed commented Jun 25, 2013

It would be nice to be able to start the server on an existing file descriptor instead of having it opening one based on a port number. This can be usefull e.g. with Circus: Circus will manage the port (and call listen on it) and fork the server, allowing it to accept on the FD shared between possibly multiple snap workers.

@pheaver
Copy link

pheaver commented Jun 25, 2013

i am very interested in this, too.

@gregorycollins
Copy link
Member

The new snap server will support this.

@bos
Copy link

bos commented Apr 24, 2014

Also interested.

@teh
Copy link

teh commented Feb 24, 2015

Me, too, because I want to set some non-portable flags when opening the socket such as SOCK_CLOEXEC or setFdOption (fromIntegral $ fdSocket socket) CloseOnExec True.

@gregorycollins
Copy link
Member

@teh
Copy link

teh commented Feb 24, 2015

Apologies for missing that - thank you!

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

5 participants