chiark / gitweb /
resolved: generate an explicit transaction error when we cannot reach server via TCP
authorLennart Poettering <lennart@poettering.net>
Fri, 25 Dec 2015 11:54:27 +0000 (12:54 +0100)
committerSven Eden <yamakuzure@gmx.net>
Wed, 17 May 2017 13:22:14 +0000 (15:22 +0200)
commit43a3dea4ff860a0a66be85032d6d39e73c4ffbd9
tree925d54b303fa235a821a163730edfaa375e3a9f6
parentb81e1f72c73aaee653819615faaebacc48eeb18d
resolved: generate an explicit transaction error when we cannot reach server via TCP

Previously, if we couldn't reach a server via UDP we'd generate an
MAX_ATTEMPTS transaction result, but if we couldn't reach it via TCP
we'd generate a RESOURCES transaction result. While it is OK to generate
two different errors I think, "RESOURCES" is certainly a misnomer.
Introduce a new transaction result "CONNECTION_FAILURE" instead.
src/libelogind/sd-bus/bus-common-errors.h