diff options
| author | Lennart Poettering <lennart@poettering.net> | 2022-02-03 15:57:00 +0100 |
|---|---|---|
| committer | Luca Boccassi <luca.boccassi@gmail.com> | 2022-02-04 17:43:44 +0000 |
| commit | a2012854f511c31504c52e9c90669c09ea5eb572 (patch) | |
| tree | b3b29fd7aaa7d5ea535bff61e0219c199fbebd13 /src/stdio-bridge | |
| parent | 05aca544685cc0e5b8587dc346c548b3d14b3c18 (diff) | |
| download | systemd-a2012854f511c31504c52e9c90669c09ea5eb572.tar.gz | |
man: systemd-stdio-bridge doesn't connect "two busses"
In D-Bus, clients connect to a bus (the usual case), or use direct
questions to each other (the unusual case). A bus is a program one can
connect to and implemented by dbus-daemon or dbus-broker. HOwever,
busses never connect between each other, that doesn't exist. Hence don't
claim so.
This is probably confusion about the fact that sd-bus calls D-Bus
connection objects just "sd_bus" for simplicity, given they are used in
99% of the cases to connect to a bus — only in exceptional cases they
are used for direct connections between peers without involving a bus.
Follow-up for b7bb58ef70b0c876941a1c31ed4e2f5f1dc5ed0e
Diffstat (limited to 'src/stdio-bridge')
| -rw-r--r-- | src/stdio-bridge/stdio-bridge.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/stdio-bridge/stdio-bridge.c b/src/stdio-bridge/stdio-bridge.c index 33701e775e..c851059a09 100644 --- a/src/stdio-bridge/stdio-bridge.c +++ b/src/stdio-bridge/stdio-bridge.c @@ -27,7 +27,7 @@ static bool arg_user = false; static int help(void) { printf("%s [OPTIONS...]\n\n" - "Forward messages between two D-Bus busses via a pipe or socket.\n\n" + "Forward messages between a pipe or socket and a D-Bus bus.\n\n" " -h --help Show this help\n" " --version Show package version\n" " -p --bus-path=PATH Path to the bus address (default: %s)\n" |