diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-02-11 21:58:46 -0500 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-02-11 21:58:46 -0500 |
| commit | b266400c927a219f99924b4a070ee61e4936af07 (patch) | |
| tree | 762abff1a01f69c30f11605fd4b340b41ff1795a /man | |
| parent | 1d00ee20319cf582e302148f4fb53cf963943038 (diff) | |
| parent | 9ca6ff50ab7af9d122521c5bb9cc8201cb38181a (diff) | |
| download | systemd-b266400c927a219f99924b4a070ee61e4936af07.tar.gz | |
Merge pull request #2590 from zonque/bus-endpoint-removal
Remove kdbus custom endpoint support
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.service.xml | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 5fdf631cf5..e55534700a 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -273,42 +273,6 @@ </varlistentry> <varlistentry> - <term><varname>BusPolicy=</varname></term> - - <listitem><para>If specified, a custom kdbus - endpoint will be created and installed as the default bus node - for the service. Such a custom endpoint can hold an own set of - policy rules that are enforced on top of the bus-wide ones. - The custom endpoint is named after the service it was created - for, and its node will be bind-mounted over the default bus - node location, so the service can only access the bus through - its own endpoint. Note that custom bus endpoints default to a - "deny all" policy. Hence, if at least one - <varname>BusPolicy=</varname> directive is given, you have to - make sure to add explicit rules for everything the service - should be able to do.</para> - <para>The value of this directive is comprised - of two parts; the bus name, and a verb to - specify to granted access, which is one of - <option>see</option>, - <option>talk</option>, or - <option>own</option>. - <option>talk</option> implies - <option>see</option>, and <option>own</option> - implies both <option>talk</option> and - <option>see</option>. - If multiple access levels are specified for the - same bus name, the most powerful one takes - effect. - </para> - <para>Examples:</para> - <programlisting>BusPolicy=org.freedesktop.systemd1 talk</programlisting> - <programlisting>BusPolicy=org.foo.bar see</programlisting> - <para>This option is only available on kdbus enabled systems.</para> - </listitem> - </varlistentry> - - <varlistentry> <term><varname>ExecStart=</varname></term> <listitem><para>Commands with their arguments that are executed when this service is started. The value is split into |