summaryrefslogtreecommitdiff
path: root/configure.ac
diff options
context:
space:
mode:
authorSimon McVittie <simon.mcvittie@collabora.co.uk>2014-10-29 14:10:48 +0000
committerSimon McVittie <simon.mcvittie@collabora.co.uk>2014-10-29 14:10:48 +0000
commitf541722f5ac0b2ee2d9eab6b9a77aa1f1c174817 (patch)
tree86edaf8e53665e1dbe8fad8c919bdb1eccb29ded /configure.ac
parentdab9cbc5026d896f5ec15a3c5ff69ed18854c7e2 (diff)
downloaddbus-f541722f5ac0b2ee2d9eab6b9a77aa1f1c174817.tar.gz
Use a better NoReply message for disconnection with reply pending
As an implementation detail, dbus-daemon handles this situation by artificially triggering a timeout (even if its configured timeout for method calls is in fact infinite). However, using the same debug message for both is misleading, and can lead people who are debugging a service crash to blame dbus-daemon instead, wasting their time. Bug: https://bugs.freedesktop.org/show_bug.cgi?id=76112
Diffstat (limited to 'configure.ac')
-rw-r--r--configure.ac1
1 files changed, 1 insertions, 0 deletions
diff --git a/configure.ac b/configure.ac
index 89e4d2ec..de34d3e2 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1779,6 +1779,7 @@ dbus-1.pc
dbus-1-uninstalled.pc
test/data/valid-config-files/debug-allow-all.conf
test/data/valid-config-files/debug-allow-all-sha1.conf
+test/data/valid-config-files/finite-timeout.conf
test/data/valid-config-files/incoming-limit.conf
test/data/valid-config-files-system/debug-allow-all-pass.conf
test/data/valid-config-files-system/debug-allow-all-fail.conf