From: Zbigniew Jędrzejewski-Szmek Date: Wed, 22 May 2019 09:09:36 +0000 (+0200) Subject: man: reword systemd.socket(5) description to avoid "file" when talking about services X-Git-Tag: v243-rc1~391^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=847af199e5af43149eb07622e49952fd8dde4768;p=thirdparty%2Fsystemd.git 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 --- diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index e29602b0681..84faf89c2e6 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. - For each socket file, a matching service file must exist, + For each socket unit, a matching service unit must exist, describing the service to start on incoming traffic on the socket (see systemd.service5 - 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 described below. Depending on the setting of the @@ -66,7 +66,7 @@ socket file foo.socket needs a matching service foo.service if is set. If - is set, a service template file + is set, a service template foo@.service must exist from which services are instantiated for each incoming connection.