-
Notifications
You must be signed in to change notification settings - Fork 3
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
support listener names for sd-listen #5
Comments
How do I test those names and multi-socket mode with |
Rememer you need to kick off one request for it to start. As an example, my
|
What user-facing API do you propose? Something like |
I think I was mostly thinking about supporting parsing |
Hmmh, I don't quite like the current We shouldn't have to (let the user) decide about this, I'd feel more comfortable changing the API to return an enum which is either And maybe expose another function giving you an API to enumerate the list of FDs passed, as well as getting their names, in addition to the |
How should it determine whether a file descriptor is a Tcp or Unix socket? Using additional syscall ( |
That only identifies the address family. You may also want |
|
Implemented, including additional feature: |
Thanks! Just tested it now, looks good. I noticed you did prepare a 0.4.0 version number, however there doesn't seem to be a tag or release published to crates.io yet. Can you do this? Thanks! |
Published v0.4.1 with this and also better errors. |
Thanks! |
As described in https://mgdm.net/weblog/systemd-socket-activation/, it's possible to receive multiple sockets, and they can have names attached.
This can be used to have multiple
.socket
files (with differentFileDescriptorName=
values).For example, one socket could be used for
http
, and another one forhttps
connections.The text was updated successfully, but these errors were encountered: