From a7c0e5d714512dc3f9fe30c136778257246f3279 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 26 Nov 2013 02:25:34 +0100 Subject: [PATCH] man: explain the precise syntax and feature set of unit names at the end of the man page, given that it is detail information --- man/systemctl.xml | 35 ++++++++++++++++++++++------------- 1 file changed, 22 insertions(+), 13 deletions(-) diff --git a/man/systemctl.xml b/man/systemctl.xml index 58b2c2ad9..567f39839 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -63,19 +63,6 @@ along with systemd; If not, see . introspect and control the state of the systemd1 system and service manager. - - For unit commands, the NAME represents full name of the unit. - -systemctl start foo.service - - For unit file commands, the NAME represents the full name of the unit file, or the absolute path to the unit file. - -systemctl start /path/to/foo.service - - While working with services/service files, systemctl implicitly appends the ".service" suffix when it is missing. - -systemctl start foo - @@ -1307,6 +1294,28 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service + + Parameter Syntax + + For unit commands the specified + NAME should be the full name of the + unit, or an abbreviated name which is automatically extended with + the .service suffix. + # systemctl start foo.service is equivalent to: + # systemctl start foo + Note that (absolute) paths to device nodes are automatically converted to device unit names, and other (absolute) paths to mount unit names. + # systemctl status /dev/sda +# systemctl status /home is equivalent to: + # systemctl status dev-sda.device +# systemctl status home.mount + + For unit file commands the + specified NAME should be the full name + of the unit file, or the absolute path to the unit file. + # systemctl link /path/to/foo.service + + + -- 2.30.2