X-Git-Url: http://git.ipfire.org/?a=blobdiff_plain;f=man%2Fsd_bus_set_watch_bind.xml;h=5638cdc0a62e4cbc503e2976457ac601b6352304;hb=c53da7ed02a5d732c9449f79c19675b90a6032e3;hp=d19f6b92129217c52e8c179bd14daca3846cbda4;hpb=fdbbee37d5af7fdcb3987d732f27f4fd7d1615d9;p=thirdparty%2Fsystemd.git diff --git a/man/sd_bus_set_watch_bind.xml b/man/sd_bus_set_watch_bind.xml index d19f6b92129..5638cdc0a62 100644 --- a/man/sd_bus_set_watch_bind.xml +++ b/man/sd_bus_set_watch_bind.xml @@ -1,12 +1,10 @@ - - + + + - - - + sd_bus_set_watch_bind @@ -50,7 +48,7 @@ socket binding for a bus connection object. If the b is true, the feature is enabled, otherwise disabled (which is the default). When enabled, and the selected bus address refers to an AF_UNIX socket in the file system which does not exist while the connection attempt is made an - inotify7 watch is installed on + inotify7 watch is installed on it, waiting for the socket to appear. As soon as the socket appears the connection is made. This functionality is useful in particular in early-boot programs that need to run before the system bus is available, but want to connect to it the instant it may be connected to. @@ -58,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_add_match_async3 or - sd_bus_request_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_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. Use sd_bus_is_ready3 to determine whether the connection is fully established, i.e. whether the peer socket has been bound, connected to @@ -82,31 +80,25 @@ Return Value - On success, these functions return 0 or a positive integer. On failure, they return a negative errno-style - error code. - + On success, these functions return 0 or a positive integer. On failure, they return a negative + errno-style error code. - - Errors + + Errors - Returned errors may indicate the following problems: + Returned errors may indicate the following problems: - - - -ECHILD + + + -ECHILD - The bus connection has been created in a different process. - - + The bus connection has been created in a different process. + + + - - Notes - - sd_bus_set_watch_bind() and sd_bus_get_watch_bind() are available as - a shared library, which can be compiled and linked to with the libsystemd pkg-config1 file. - + See Also @@ -114,7 +106,7 @@ systemd1, sd-bus3, - inotify7, + inotify7, sd_bus_call3, sd_bus_add_match3, sd_bus_request_name3,