From 4a5a01ccdd95000d60b07a9d3b1babe74598aa58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Thu, 25 Jun 2020 14:41:05 +0200 Subject: [PATCH] man: reword awkward sentence --- man/sd_bus_set_watch_bind.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/man/sd_bus_set_watch_bind.xml b/man/sd_bus_set_watch_bind.xml index 9625652d2a..5638cdc0a6 100644 --- a/man/sd_bus_set_watch_bind.xml +++ b/man/sd_bus_set_watch_bind.xml @@ -56,18 +56,18 @@ sd_bus_get_watch_bind() may be used to query the current setting of this feature. It returns zero when the feature is disabled, and positive if enabled. - Note that no timeout is applied while it is waited for the socket to appear. This means that any synchronous - remote operation (such as + Note that no timeout is applied while we wait for the socket to appear. This means that any + synchronous remote operation (such as sd_bus_call3, sd_bus_add_match3 or - sd_bus_request_name3), that is - used on a connection with this feature enabled that is not established yet might block unbounded if the socket is - never created. However, asynchronous remote operations (such as + sd_bus_request_name3), + that is used on a connection with this feature enabled that hasn't been established yet, might block + forever if the socket is never created. However, asynchronous remote operations (such as sd_bus_send3, sd_bus_call_async3, - sd_bus_add_match_async3) do - not block in this case, and safely enqueue the requested operations to be dispatched the instant the connection is - set up. + sd_bus_add_match_async3) + do not block in this case, and safely enqueue the requested operations to be dispatched the instant the + connection is set up. Use sd_bus_is_ready3 to determine whether the connection is fully established, i.e. whether the peer socket has been bound, connected to