<div style="white-space:pre-wrap">Couple tips;<br><br>systemctl has an is-enabled command.<br><br>systemctl is-enabled httpd<br><br>Using a -l flag on systemctl status gets you more info on what your service did after you started it<br><br>systemctl status -l httpd<br><br>Finally, journalctl has the ability to only return entries for a particular service or timer, etc.<br><br>journalctl _SYSTEMD_UNIT=httpd.service<br><br>Not advocating for an init system - just a couple of tips. Hth<br><br>-Zach</div><br><div class="gmail_quote"><div dir="ltr">On Mon, Mar 7, 2016 at 8:40 AM Rick Hornsby <<a href="mailto:richardjhornsby@gmail.com">richardjhornsby@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Mar 7, 2016, at 00:16, Jacob Ulrich <contact@peachchannel.lol> wrote:<br>
><br>
> Does anybody else dislike systemd with a passion? I ask just because I<br>
> see a lot of RHEL related talk on this list. Sorry if this is<br>
> irrelevant. I mostly use GNU/Linux as a hobby.<br>
<br>
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.<br>
<br>
But instead of<br>
<br>
chkconfig --list ntpd<br>
<br>
Now it's<br>
<br>
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?<br>
<br>
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.<br>
<br>
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.<br>
<br>
It also doesn't help that we have both 'systemctl' and 'sysctl' - each of which do completely different things.<br>
<br>
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.<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" rel="noreferrer" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div>