Comment by frizlab 1 year ago It’s because service was the other way around, I’m sure. 2 comments frizlab Reply DHowett 1 year ago systemd services are named "foo.service", and you do not need to specify the ".service" in almost any case. tremon 1 year ago They're referring to Debian's service(8) command. NAME service - run a System V init script SYNOPSIS service SCRIPT COMMAND [OPTIONS] (the manpage wasn't updated, but the same command also supports systemd services nowadays)
DHowett 1 year ago systemd services are named "foo.service", and you do not need to specify the ".service" in almost any case. tremon 1 year ago They're referring to Debian's service(8) command. NAME service - run a System V init script SYNOPSIS service SCRIPT COMMAND [OPTIONS] (the manpage wasn't updated, but the same command also supports systemd services nowadays)
tremon 1 year ago They're referring to Debian's service(8) command. NAME service - run a System V init script SYNOPSIS service SCRIPT COMMAND [OPTIONS] (the manpage wasn't updated, but the same command also supports systemd services nowadays)
systemd services are named "foo.service", and you do not need to specify the ".service" in almost any case.
They're referring to Debian's service(8) command.
(the manpage wasn't updated, but the same command also supports systemd services nowadays)