diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-05-22 11:09:36 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2019-05-22 16:28:02 +0200 |
| commit | 847af199e5af43149eb07622e49952fd8dde4768 (patch) | |
| tree | c5544b8fff3184ffaae21706220e7c42447baae2 /man | |
| parent | 7cc5ef5f1811c539ae7f20255c2a093f413cc64f (diff) | |
| download | systemd-847af199e5af43149eb07622e49952fd8dde4768.tar.gz | |
man: reword systemd.socket(5) description to avoid "file" when talking about services
This text was written a long time ago, when we mostly talked about "service
files". Strictly speaking, we don't need a "file", because the service might
be just an instance of a template, or an alias to another service. So let's use
the more modern parlance of "service units".
https://bugzilla.redhat.com/show_bug.cgi?id=1623781#c21
Diffstat (limited to 'man')
| -rw-r--r-- | man/systemd.socket.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index e29602b068..84faf89c2e 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -51,11 +51,11 @@ which configure resource control settings for the processes of the socket.</para> - <para>For each socket file, a matching service file must exist, + <para>For each socket unit, a matching service unit must exist, describing the service to start on incoming traffic on the socket (see <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry> - for more information about .service files). The name of the + for more information about .service units). The name of the .service unit is by default the same as the name of the .socket unit, but can be altered with the <option>Service=</option> option described below. Depending on the setting of the @@ -66,7 +66,7 @@ socket file <filename>foo.socket</filename> needs a matching service <filename>foo.service</filename> if <option>Accept=no</option> is set. If - <option>Accept=yes</option> is set, a service template file + <option>Accept=yes</option> is set, a service template <filename>foo@.service</filename> must exist from which services are instantiated for each incoming connection.</para> |