security-context-v1: clarify close_fd behavior

Signed-off-by: Julian Orth <ju.orth@gmail.com>
This commit is contained in:
Julian Orth 2024-04-24 10:44:59 +02:00 committed by Daniel Stone
parent 6f5772fd69
commit f30b27a0ee

View file

@ -68,7 +68,7 @@
sent by the client. In other words, the client must call bind(2) and sent by the client. In other words, the client must call bind(2) and
listen(2) before sending the FD. listen(2) before sending the FD.
close_fd is a FD closed by the client when the compositor should stop close_fd is a FD that will signal hangup when the compositor should stop
accepting new connections on listen_fd. accepting new connections on listen_fd.
The compositor must continue to accept connections on listen_fd when The compositor must continue to accept connections on listen_fd when
@ -79,7 +79,7 @@
</description> </description>
<arg name="id" type="new_id" interface="wp_security_context_v1"/> <arg name="id" type="new_id" interface="wp_security_context_v1"/>
<arg name="listen_fd" type="fd" summary="listening socket FD"/> <arg name="listen_fd" type="fd" summary="listening socket FD"/>
<arg name="close_fd" type="fd" summary="FD closed when done"/> <arg name="close_fd" type="fd" summary="FD signaling when done"/>
</request> </request>
</interface> </interface>