"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">

<busconfig>

  <type>session</type>

       the behavior of child processes. -->

  <keep_umask/>

  <listen>unix:tmpdir=/tmp</listen>

  <servicedir>@testdir@/services</servicedir>

       interfere with user's real keyrings, as well as causing long delays

       during D-BUS activation -->

  <policy context="default">

    <allow send_destination="*" eavesdrop="true"/>

    <allow eavesdrop="true"/>

    <allow own="*"/>

  </policy>

  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

       with essentially infinite limits, since the bus is just running 

       as the user anyway, using up bus resources is not something we need 

       to worry about. In some cases, we do set the limits lower than 

       "all available memory" if exceeding the limit is almost certainly a bug, 

       having the bus enforce a limit is nicer than a huge memory leak. But the 

       intent is that these limits should never be hit. -->

  <limit name="max_incoming_bytes">1000000000</limit>

  <limit name="max_incoming_unix_fds">250000000</limit>

  <limit name="max_outgoing_bytes">1000000000</limit>

  <limit name="max_outgoing_unix_fds">250000000</limit>

  <limit name="max_message_size">1000000000</limit>

  <limit name="max_message_unix_fds">4096</limit>

  <limit name="service_start_timeout">120000</limit>  

  <limit name="auth_timeout">240000</limit>

  <limit name="max_completed_connections">100000</limit>  

  <limit name="max_incomplete_connections">10000</limit>

  <limit name="max_connections_per_user">100000</limit>

  <limit name="max_pending_service_starts">10000</limit>

  <limit name="max_names_per_connection">50000</limit>

  <limit name="max_match_rules_per_connection">50000</limit>

  <limit name="max_replies_per_connection">50000</limit>

</busconfig>