On Lu, 30 dec 19, 10:01:55, Gene Heskett wrote: > But it sure would be nice if the manpages were a little more obvious. > :) Options seem to be well explained but commonly used examples that > one can play with to learn how it works are thin. A good tut that > passed as a manpage would likely reduce the objection chatter a lot by > showing that it can be a better way to do things. For a quick start you only need 'systemctl' with the 'status', 'start', 'stop', 'restart', 'reload', 'enable' and 'disable' commands, possibly also 'mask' (didn't need it so far, 'disable' was always sufficient when applied correctly[1]). The man page for 'systemctl' has a detailed example for the 'status' command, the only one where the output is not so easy to understand at first look. For more advanced stuff the wiki pages on systemd seem to be a good start[2]. [1] a service can also be enabled via a .socket unit and systemd does warn if you only disable the .service unit for a service that also has a .socket unit. [2] https://wiki.debian.org/systemd Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Attachment:
signature.asc
Description: PGP signature