Simon McVittie f541722f5a 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		2014-10-29 14:10:48 +00:00
..
basic.d	2003-04-02 Havoc Pennington <hp@redhat.com>	2003-04-02 21:43:29 +00:00
system.d	2003-09-21 Havoc Pennington <hp@pobox.com>	2003-09-21 19:53:56 +00:00
.gitignore	.gitignore: ignore incoming-limit.conf file	2014-06-11 11:14:05 +01:00
basic.conf	2005-01-18 Havoc Pennington <hp@redhat.com>	2005-01-18 20:42:15 +00:00
check-own-rules.conf	test: enforce own_prefix policy rules	2012-03-22 11:51:23 +00:00
debug-allow-all-sha1.conf.in	Merge tests' cmake and autotools bus configuration	2011-09-28 19:00:56 +01:00
debug-allow-all.conf.in	Merge tests' cmake and autotools bus configuration	2011-09-28 19:00:56 +01:00
entities.conf	2003-04-12 Havoc Pennington <hp@pobox.com>	2003-04-12 18:32:11 +00:00
finite-timeout.conf.in	Use a better NoReply message for disconnection with reply pending	2014-10-29 14:10:48 +00:00
incoming-limit.conf.in	Use TEST_LISTEN in incoming-listen.conf.in instead of unix only hardcoded address	2013-10-10 15:38:50 +02:00
many-rules.conf	test: parse own_prefix policy rules	2012-03-22 11:50:27 +00:00