I've gotten pretty far with: systemctl status, systemctl status <service name>, systemctl restart <service name>, and journalctl -u <service name>.
On Sat, Oct 16, 2021, 21:55 Keith Lofstrom <[email protected]> wrote: > I've used linux for decades, and Unix for almost half a > century. systemd is different, and not nearly as well > documented. I'd love to find a "recipe book": > > systemd for dinosaurs > > which explains the user- and sysadmin- facing differences, > perhaps with pages indexed by the old commands (all the > way back to AT&T Unix), explaining how to use systemd > commands to accomplish similar (or better) results. > > Perhaps also some shell scripts for /usr/local/bin named > like the ancient commands, which transmogrify command line > arguments into a plausible systemd command line, print it > out for the user with a short explanation, and ask > "run this systemd command yes or no?" > > Over a life, memory grows like an onion; in old age, > memories peel off the same way. Tools that help grandma > keep her servers running means fewer plaintive phone calls > at 3am, interrupting important video games. > > Keith > > -- > Keith Lofstrom [email protected] >
