From: Luca Bruno <lucab@debian.org>
Date: Tue, 28 Jun 2016 18:14:08 +0000 (+0200)
Subject: man: clarify NotifyAccess overriding (#3620)
X-Git-Tag: v231~106
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=aa4f6cf12c474aa2c6535e4b2c434ea39c9d568c;p=thirdparty%2Fsystemd.git

man: clarify NotifyAccess overriding (#3620)

Type=notify has a magic overriding case where a NotifyAccess=none
is turned into a NotifyAccess=main for sanity purposes.
This makes docs more clear about such behavior:
https://github.com/systemd/systemd/blob/2787d83c28b7565ea6f80737170514e5e6186917/src/core/service.c#L650:L651
---

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 6e969abc258..70f12b2d326 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -202,8 +202,9 @@
         notification message has been sent. If this option is used,
         <varname>NotifyAccess=</varname> (see below) should be set to
         open access to the notification socket provided by systemd. If
-        <varname>NotifyAccess=</varname> is not set, it will be
-        implicitly set to <option>main</option>. Note that currently
+        <varname>NotifyAccess=</varname> is missing or set to
+        <option>none</option>, it will be forcibly set to
+        <option>main</option>. Note that currently
         <varname>Type=</varname><option>notify</option> will not work
         if used in combination with
         <varname>PrivateNetwork=</varname><option>yes</option>.</para>