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

Document non-determinism for binding systemd sockets #8146

Closed
twisted-trac opened this issue Dec 18, 2015 · 0 comments · Fixed by #11691
Closed

Document non-determinism for binding systemd sockets #8146

twisted-trac opened this issue Dec 18, 2015 · 0 comments · Fixed by #11691

Comments

@twisted-trac
Copy link

jml's avatar @jml reported
Trac ID trac#8146
Type enhancement
Created 2015-12-18 12:33:42Z

The systemd documentation says:

If multiple socket units activate the same service, the order of the file descriptors passed to its main process is undefined.

(see http://www.freedesktop.org/software/systemd/man/sd_listen_fds.html)

This means that if a Twisted process uses multiple systemd endpoints, it cannot be sure that the right sockets are bound to the right services.

We should document this limitation in Twisted.

c.f. https://clusterhq.atlassian.net/browse/FLOC-3712.

Searchable metadata
trac-id__8146 8146
type__enhancement enhancement
reporter__jml jml
priority__low low
milestone__None None
branch__ 
branch_author__ 
status__new new
resolution__None None
component__core core
keywords__documentation documentation
time__1450442022165513 1450442022165513
changetime__1450442022165513 1450442022165513
version__None None
owner__None None

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

Successfully merging a pull request may close this issue.

1 participant