diff options
author | Alexander Larsson <alexl@redhat.com> | 2016-05-02 10:46:51 +0200 |
---|---|---|
committer | Alexander Larsson <alexl@redhat.com> | 2016-05-02 10:46:51 +0200 |
commit | 2f465215e23f956419b9ae905ae3c94717bc2de1 (patch) | |
tree | 6deb56ee722be63830810d07b30713ca2bb75130 /tests | |
parent | e7cc0c3db9f8d5a6930f2c34b52e5a49a8e689ec (diff) | |
download | xdg-app-2f465215e23f956419b9ae905ae3c94717bc2de1.tar.gz |
Add some missing files from the tests
Diffstat (limited to 'tests')
-rw-r--r-- | tests/session.conf.in | 56 |
1 files changed, 56 insertions, 0 deletions
diff --git a/tests/session.conf.in b/tests/session.conf.in new file mode 100644 index 0000000..307f84a --- /dev/null +++ b/tests/session.conf.in @@ -0,0 +1,56 @@ +<!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> + + <!-- If we fork, keep the user's original umask to avoid affecting + the behavior of child processes. --> + <keep_umask/> + + <listen>unix:tmpdir=/tmp</listen> + + <servicedir>@testdir@/services</servicedir> + + <!-- disabled for now; this causes gnome-keyring to be spawned, which can + interfere with user's real keyrings, as well as causing long delays + during D-BUS activation --> + <!-- <standard_session_servicedirs /> --> + + <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> + + <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include> + + <!-- For the session bus, override the default relatively-low limits + 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. --> + + <!-- the memory limits are 1G instead of say 4G because they can't exceed 32-bit signed int max --> + <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> |