I'm trying to learn about rsyslog. On one of my linux boxes, I think that
rsyslog has been configured to run through systemd based on this output:
>systemctl status rsyslog rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled) Active: active (running) since Tue 2017-01-10 11:28:07 PST; 3 months 19 days ago Main PID: 954 (rsyslogd) CGroup: /system.slice/rsyslog.service L954 /sbin/rsyslogd -n >ps ax | grep syslog 954 ? Ssl 6:22 /sbin/rsyslogd -n
On the other linux box, though, systemv (systemctl is not present) seems unaware that
rsyslogd is running:
[root@box ~]# service --status-all | grep -i syslog 2>&1 [root@box ~]# ps ax | grep -i syslog 7866 ? Sl 1:49 /sbin/rsyslogd -n -c5 -i /var/run/syslogd.pid
Why this disparity?
On the second box, is the fact that rsyslogd is running but not "found" by
service evidence that it was spawned "manually" from the command-line and not configured through one of
service's init.d scripts? (Sorry if my terminology is primitive).
What I actually wanted to achieve was: on the second box, I wanted to restart rsyslog, and I expected to do so by running something like
service rsyslog restart. But not finding rsyslog when I ran
service --status-all led me down this detour.
Box 1 configuration:
>uname -a Linux box1 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux >lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: Fedora Description: Fedora release 20 (Heisenbug) Release: 20 Codename: Heisenbug
Box 2 configuration:
Linux box2 2.6.37+ #2 Tue Apr 18 03:07:09 PDT 2017 armv7l GNU/Linux