diff options
| author | Havoc Pennington <hp@redhat.com> | 2003-04-01 05:33:01 +0000 |
|---|---|---|
| committer | Havoc Pennington <hp@redhat.com> | 2003-04-01 05:33:01 +0000 |
| commit | 44ed933284589134603913b05f55ca55e8c5a566 (patch) | |
| tree | 7091c28eba6a2d93cd02ca80c39b3175ccca06f5 /doc/config-file.txt | |
| parent | 8dfe82beb530aefce505a9bf915a749647e7183f (diff) | |
2003-04-01 Havoc Pennington <hp@pobox.com>
* dbus/dbus-server.c (dbus_server_set_auth_mechanisms): new
function
* dbus/dbus-auth.c (_dbus_auth_set_mechanisms): new
* dbus/dbus-internals.c (_dbus_dup_string_array): new function
* dbus/dbus-sysdeps.c (_dbus_listen_unix_socket): chmod the
socket 0777, and unlink any existing socket.
* bus/bus.c (bus_context_new): change our UID/GID and fork if
the configuration file so specifies; set up auth mechanism
restrictions
* bus/config-parser.c (bus_config_parser_content): add support
for <fork> option and fill in code for <auth>
* bus/system.conf.in: add <fork/> to default configuration,
and limit auth mechanisms to EXTERNAL
* doc/config-file.txt (Elements): add <fork>
* dbus/dbus-sysdeps.c (_dbus_become_daemon): new function
(_dbus_change_identity): new function
Diffstat (limited to 'doc/config-file.txt')
| -rw-r--r-- | doc/config-file.txt | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/config-file.txt b/doc/config-file.txt index 5502c82b..b8230aab 100644 --- a/doc/config-file.txt +++ b/doc/config-file.txt @@ -53,6 +53,15 @@ Elements: The last <user> entry in the file "wins", the others are ignored. + The user is changed after the bus has completed initialization. + So sockets etc. will be created before changing user, but no + data will be read from clients before changing user. + + <fork> + + If present, the bus daemon becomes a real daemon (forks + into the background, etc.) + <listen> Add an address that the bus should listen on. The @@ -72,6 +81,7 @@ Elements: Lists permitted authorization mechanisms. If this element doesn't exist, then all known mechanisms are allowed. If there are multiple <auth> elements, the last one wins (they are not merged). + The order in which mechanisms are listed is not meaningful. Example: <auth>EXTERNAL</auth> Example: <auth>DBUS_COOKIE_SHA1</auth> |