On Mar 31, 2015 7:55 PM, "Daniel Frey" <djqf...@gmail.com> wrote: > > On 03/17/2015 10:20 AM, Rich Freeman wrote: > > The cheat sheets are useful for reference, but I'd strongly encourage > > anybody using systemd to get a decent understanding of the > > fundamentals. > > Oh, certainly - but going in completely blind and being stuck for 15 > minutes trying to do a simple task sucks. I'm not saying that a > cheatsheet is enough to avoid reading manpages, but at least it's a > start where users can find information to do basic stuff with systemd. > I'm also not talking about a cheatsheet about writing units/services/etc. > > When I did the switch there wasn't anything in the gentoo-related wikis > for even things like starting kdm. This is what I'm talking about - how > to list services, start and stop things - basic stuff. > > Anyway, I've finally gotten around to putting together a short > cheatsheet @ https://wiki.gentoo.org/wiki/OpenRC_to_Systemd_Cheatsheet .
Thanks for doing this, I think it will help all the people switching to systemd from OpenRC in Gentoo. However, I think the zap command is a little misleading, even with the note stating that is no "exactly" the same. AFAIR, zap doesn't do anything to the processes of a service; it just "zaps" back the internal state of OpenRC as if the service is stopped. It's needed because OpenRC cannot really follow the status of its services, so sometimes they die and OpenRC is none the wiser, and you need to zap the service because trying to stopping them would fail. With systemd you don't need this, since it can track the real state of its services thanks to cgroups. And kill *really* kills all the processes associated to a service, something that OpenRC, by design, cannot do. I believe the difference is substantial enough that it should not be stated that they are equivalent. But except for that minor nitpick, it looks great. Thanks again. Regards.
