diff options
| author | Alan Jenkins <alan.christopher.jenkins@gmail.com> | 2017-12-16 10:48:12 +0000 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2017-12-16 11:48:12 +0100 |
| commit | 3f2d136505370bb2c8ccd6f66a33c559847b3ab4 (patch) | |
| tree | 34b93787a8ae135229b00bd22fe36d222a84afa6 /man/systemd-socket-activate.xml | |
| parent | 6671e818e93ee1b3caf071d3aff284fb8fa85f00 (diff) | |
| download | systemd-3f2d136505370bb2c8ccd6f66a33c559847b3ab4.tar.gz | |
man: generalize "binary" to "program" (#7668)
Systemd services are permitted to be scripts, as well as binary
executables.
The same also applies to the underlying /sbin/mount and /sbin/swapon.
It is not necessary for the user to consider what type of program file
these are. Nor is it necessary with systemd-nspawn, to distinguish between
init as a "binary" v.s. a user-specified "program".
Also fix a couple of grammar nits in the modified sentences.
Diffstat (limited to 'man/systemd-socket-activate.xml')
| -rw-r--r-- | man/systemd-socket-activate.xml | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/man/systemd-socket-activate.xml b/man/systemd-socket-activate.xml index 79e35dd30e..ff9e7758b3 100644 --- a/man/systemd-socket-activate.xml +++ b/man/systemd-socket-activate.xml @@ -62,8 +62,9 @@ <refsect1> <title>Description</title> - <para><command>systemd-socket-activate</command> may be used to launch a socket-activated service binary from the command - line for testing purposes. It may also be used to launch individual instances of the service binary per connection. + <para><command>systemd-socket-activate</command> may be used to launch a socket-activated service program from the + command line for testing purposes. It may also be used to launch individual instances of the service program per + connection. </para> <para>The daemon to launch and its options should be specified @@ -97,7 +98,7 @@ <term><option>-a</option></term> <term><option>--accept</option></term> - <listitem><para>Launch an instance of the service binary for each connection and pass the connection + <listitem><para>Launch an instance of the service program for each connection and pass the connection socket.</para></listitem> </varlistentry> |