From b678359235008e795d7da0ef12935e652c7109f6 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Wed, 13 Feb 2019 10:27:36 +0100 Subject: [PATCH] man: use for SD_BUS_ERROR_* and SD_BUS_NAME_* constants This moves them to the right section in systemd.directives. --- man/sd-bus-errors.xml | 62 ++++++++++++++++++++++----------------------- man/sd_bus_request_name.xml | 14 +++++----- 2 files changed, 38 insertions(+), 38 deletions(-) diff --git a/man/sd-bus-errors.xml b/man/sd-bus-errors.xml index c896511..a94022c 100644 --- a/man/sd-bus-errors.xml +++ b/man/sd-bus-errors.xml @@ -112,7 +112,7 @@ - SD_BUS_ERROR_FAILED + SD_BUS_ERROR_FAILED A generic error indication. See the error message for further details. This error name should be avoided, in favor of a more expressive error @@ -120,134 +120,134 @@ - SD_BUS_ERROR_NO_MEMORY + SD_BUS_ERROR_NO_MEMORY A memory allocation failed, and the requested operation could not be completed. - SD_BUS_ERROR_SERVICE_UNKNOWN + SD_BUS_ERROR_SERVICE_UNKNOWN The contacted bus service is unknown and cannot be activated. - SD_BUS_ERROR_NAME_HAS_NO_OWNER + SD_BUS_ERROR_NAME_HAS_NO_OWNER The specified bus service name currently has no owner. - SD_BUS_ERROR_NO_REPLY + SD_BUS_ERROR_NO_REPLY A message did not receive a reply. This error is usually generated after a timeout. - SD_BUS_ERROR_IO_ERROR + SD_BUS_ERROR_IO_ERROR Generic input/output error, for example when accessing a socket or other I/O context. - SD_BUS_ERROR_BAD_ADDRESS + SD_BUS_ERROR_BAD_ADDRESS The specified D-Bus bus address string is malformed. - SD_BUS_ERROR_NOT_SUPPORTED + SD_BUS_ERROR_NOT_SUPPORTED The requested operation is not supported on the local system. - SD_BUS_ERROR_LIMITS_EXCEEDED + SD_BUS_ERROR_LIMITS_EXCEEDED Some limited resource has been exhausted. - SD_BUS_ERROR_ACCESS_DENIED + SD_BUS_ERROR_ACCESS_DENIED Access to a resource has been denied due to security restrictions. - SD_BUS_ERROR_AUTH_FAILED + SD_BUS_ERROR_AUTH_FAILED Authentication did not complete successfully. - SD_BUS_ERROR_NO_SERVER + SD_BUS_ERROR_NO_SERVER Unable to connect to the specified server. - SD_BUS_ERROR_TIMEOUT + SD_BUS_ERROR_TIMEOUT An operation timed out. Note that method calls which timeout generate a - SD_BUS_ERROR_NO_REPLY. + SD_BUS_ERROR_NO_REPLY. - SD_BUS_ERROR_NO_NETWORK + SD_BUS_ERROR_NO_NETWORK No network available to execute requested network operation on. - SD_BUS_ERROR_ADDRESS_IN_USE + SD_BUS_ERROR_ADDRESS_IN_USE The specified network address is already being listened on. - SD_BUS_ERROR_DISCONNECTED + SD_BUS_ERROR_DISCONNECTED The connection has been terminated. - SD_BUS_ERROR_INVALID_ARGS + SD_BUS_ERROR_INVALID_ARGS One or more invalid arguments have been passed. - SD_BUS_ERROR_FILE_NOT_FOUND + SD_BUS_ERROR_FILE_NOT_FOUND The requested file could not be found. - SD_BUS_ERROR_FILE_EXISTS + SD_BUS_ERROR_FILE_EXISTS The requested file already exists. - SD_BUS_ERROR_UNKNOWN_METHOD + SD_BUS_ERROR_UNKNOWN_METHOD The requested method does not exist in the selected interface. - SD_BUS_ERROR_UNKNOWN_OBJECT + SD_BUS_ERROR_UNKNOWN_OBJECT The requested object does not exist in the selected service. - SD_BUS_ERROR_UNKNOWN_INTERFACE + SD_BUS_ERROR_UNKNOWN_INTERFACE The requested interface does not exist on the selected object. - SD_BUS_ERROR_UNKNOWN_PROPERTY + SD_BUS_ERROR_UNKNOWN_PROPERTY The requested property does not exist in the selected interface. - SD_BUS_ERROR_PROPERTY_READ_ONLY + SD_BUS_ERROR_PROPERTY_READ_ONLY A write operation was requested on a read-only property. - SD_BUS_ERROR_UNIX_PROCESS_ID_UNKNOWN + SD_BUS_ERROR_UNIX_PROCESS_ID_UNKNOWN The requested PID is not known. - SD_BUS_ERROR_INVALID_SIGNATURE + SD_BUS_ERROR_INVALID_SIGNATURE The specified message signature is not valid. - SD_BUS_ERROR_INCONSISTENT_MESSAGE + SD_BUS_ERROR_INCONSISTENT_MESSAGE The passed message does not validate correctly. - SD_BUS_ERROR_MATCH_RULE_NOT_FOUND + SD_BUS_ERROR_MATCH_RULE_NOT_FOUND The specified match rule does not exist. - SD_BUS_ERROR_MATCH_RULE_INVALID + SD_BUS_ERROR_MATCH_RULE_INVALID The specified match rule is invalid. - SD_BUS_ERROR_INTERACTIVE_AUTHORIZATION_REQUIRED + SD_BUS_ERROR_INTERACTIVE_AUTHORIZATION_REQUIRED Access to the requested operation is not permitted. However, it might be available after interactive authentication. This is usually returned by method calls diff --git a/man/sd_bus_request_name.xml b/man/sd_bus_request_name.xml index 3c98b60..cf0b552 100644 --- a/man/sd_bus_request_name.xml +++ b/man/sd_bus_request_name.xml @@ -74,23 +74,23 @@ - SD_BUS_NAME_ALLOW_REPLACEMENT + SD_BUS_NAME_ALLOW_REPLACEMENT After acquiring the name successfully, permit other peers to take over the name when they try - to acquire it with the SD_BUS_NAME_REPLACE_EXISTING flag set. If - SD_BUS_NAME_ALLOW_REPLACEMENT is not set on the original request, such a request by other + to acquire it with the SD_BUS_NAME_REPLACE_EXISTING flag set. If + SD_BUS_NAME_ALLOW_REPLACEMENT is not set on the original request, such a request by other peers will be denied. - SD_BUS_NAME_REPLACE_EXISTING + SD_BUS_NAME_REPLACE_EXISTING Take over the name if it is already acquired by another peer, and that other peer has permitted - takeover by setting SD_BUS_NAME_ALLOW_REPLACEMENT while acquiring it. + takeover by setting SD_BUS_NAME_ALLOW_REPLACEMENT while acquiring it. - SD_BUS_NAME_QUEUE + SD_BUS_NAME_QUEUE Queue the acquisition of the name when the name is already taken. @@ -130,7 +130,7 @@ On success, these calls return 0 or a positive integer. On failure, these calls return a negative errno-style error code. - If SD_BUS_NAME_QUEUE is specified, sd_bus_request_name() will return + If SD_BUS_NAME_QUEUE is specified, sd_bus_request_name() will return 0 when the name is already taken by another peer and the client has been added to the queue for the name. In that case, the caller can subscribe to NameOwnerChanged signals to be notified when the name is successfully acquired. sd_bus_request_name() returns > 0 when the name has immediately -- 2.7.4