[colug-432] systemd dislike

Zach Villers zachvatwork at gmail.com
Mon Mar 7 09:06:56 EST 2016

Couple tips;

systemctl has an is-enabled command.

systemctl is-enabled httpd

Using a -l flag on systemctl status gets you more info on what your service
did after you started it

systemctl status -l httpd

Finally, journalctl has the ability to only return entries for a particular
service or timer, etc.

journalctl _SYSTEMD_UNIT=httpd.service

Not advocating for an init system - just a couple of tips. Hth


On Mon, Mar 7, 2016 at 8:40 AM Rick Hornsby <richardjhornsby at gmail.com>

> > On Mar 7, 2016, at 00:16, Jacob Ulrich <contact at peachchannel.lol> wrote:
> >
> > Does anybody else dislike systemd with a passion? I ask just because I
> > see a lot of RHEL related talk on this list. Sorry if this is
> > irrelevant. I mostly use GNU/Linux as a hobby.
> I'm having a hard time getting used to it.  SysV style init scripts were
> simple and effective.  I know, systemd is more powerful, and the unit files
> are supposed to be easier to deal with.
> But instead of
> chkconfig --list ntpd
> Now it's
> systemctl status ntpd - which requires reading through a bunch of output
> to figure out if your ntpd is set to start on boot or not.  Also, no more
> run levels, just a confusing pile of declared dependencies and "targets".
> I must sound really old when I ask what was wrong with my run levels 0 - 6?
> If you use the service command, the syntax is the opposite: service ntpd
> status.  I don't know why systemd does it - what seems like - backwards.
> Often when a service does not start properly, I don't get any indication.
> Have to systemctl status, and then "journalctl -xn" (no idea what
> journalctl has to do with it) to figure out what went wrong.
> It also doesn't help that we have both 'systemctl' and 'sysctl' - each of
> which do completely different things.
> To be fair to systemd, I haven't spent much time digging into these
> issues, or why things are they way they are.  I've just been dealing with
> it and grumbling.
> _______________________________________________
> colug-432 mailing list
> colug-432 at colug.net
> http://lists.colug.net/mailman/listinfo/colug-432
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.colug.net/pipermail/colug-432/attachments/20160307/19916df0/attachment.html 

More information about the colug-432 mailing list