Add socket activation for systemd and s6 #2346
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use open, listening socket file descriptors provided by the service manager
via LISTEN_FDS and LISTEN_PID environment variables.
This is how systemd tells the service about open sockets.
However, this change does not depend on systemd libraries or header.
All sockets must be mentioned exactly (IP:Port / unix-path)
in the mosquitto config file in order to be recognized.
Sockets not mentioned in the config file will be ignored.
The service/systemd directory contains an example (mosquitto.socket).
The service/s6 directory contains examples for the s6 service manager.
The new, builtin websocket mechanism can also use already open sockets.
However, the libwebsocket mchanism can not.
Signed-off-by: Christian Hohnstaedt [email protected]
Thank you for contributing your time to the Mosquitto project!
Before you go any further, please note that we cannot accept contributions if
you haven't signed the Eclipse Contributor Agreement.
If you aren't able to do that, or just don't want to, please describe your bug
fix/feature change in an issue. For simple bug fixes it is can be just as easy
for us to be told about the problem and then go fix it directly.
Then please check the following list of things we ask for in your pull request:
make test
with your changes locally?