mirror of
https://gitlab.freedesktop.org/dbus/dbus.git
synced 2026-05-03 14:48:00 +02:00
f541722f5a
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
19 lines
649 B
Text
19 lines
649 B
Text
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
|
|
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
|
|
<busconfig>
|
|
<!-- Our well-known bus type, don't change this -->
|
|
<type>session</type>
|
|
<listen>@TEST_LISTEN@</listen>
|
|
|
|
<policy context="default">
|
|
<!-- Allow everything to be sent -->
|
|
<allow send_destination="*" eavesdrop="true"/>
|
|
<!-- Allow everything to be received -->
|
|
<allow eavesdrop="true"/>
|
|
<!-- Allow anyone to own anything -->
|
|
<allow own="*"/>
|
|
</policy>
|
|
|
|
<!-- Forcibly time out method calls after 100ms -->
|
|
<limit name="reply_timeout">100</limit>
|
|
</busconfig>
|