[Cialug] systemd questions

David Champion dchamp1337 at gmail.com
Wed Jul 16 11:03:32 CDT 2014


Since it seems that most distros are going to systemd...

I'm looking for methods of various methods I'm used to with the old model.

1. service <servicename> status

This usually gave me some useful and human readable information on the
number of instances running, the number of sockets used etc.

With the replacement command:

systemctl status <servicename>

I get a response that it is running, and the top N syslog entries. No
indication about critical information I may need to easily check the
service's performance.

2. service <servicename> configtest (or checkconfig)

This usually checks all of the config files and reports back if there are
any errors, so you don't break something critical before trying to restart.
This was a little less standard. You could also type:

service <servicename>

And it would return a list of options... this makes it a lot easier,
especially for services you don't mess with quite as often.

Look like systemctl doesn't provide this at all. Some services, i.e.
nagios, now include a configtest as part of their restart process, but not
all. The answer I've found is use the specific services syntax like
"apachectl configtest"... which means we now need to hunt down and remember
each services unique command set. i.e. you type "systemctl status httpd"
but the configtest is done using apachectl, which is not intuitive.

Anyone that's been using systemd have pointers on making systemctl easier
to work with?

Here's a wiki page about systemd:

https://fedoraproject.org/wiki/Systemd

-dc


More information about the Cialug mailing list