OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: mausy5043 on February 03, 2018, 10:45:56 am

Title: Restarting services & documentation
Post by: mausy5043 on February 03, 2018, 10:45:56 am
I'm trying to figure out how to restart syslogd.
Since it is a service (and listed by service -e I thought that this would work:

Code: [Select]
$ sudo service syslogd restart
syslogd not running? (check /var/run/syslog.pid).
Starting syslogd.
syslogd: syslogd already running, pid: 7423
/etc/rc.d/syslogd: WARNING: failed to start syslogd

But apparently it doesn't.

Also using sudo pluginctl syslogd resulted in no restarting of syslogd.

Confusion...  :o

So, I'm now wondering if there is some documentation that I might have missed that lists which services, packages or plugins should be restarted in which way because there seem to be various mechanisms available with (at least to me) no apparent distinctions between the different functionalities.
Title: Re: Restarting services & documentation
Post by: franco on February 03, 2018, 03:26:23 pm
Hi there,

The older the component, the less likely the chance to operate it manually. And syslogd integration probably dates back to the first days of m0n0wall. :)

I believe /usr/local/etc/rc.configure_plugins restarts it cleanly, but will also flush all settings. /etc/rc.conf is ineffective here.

New plugins and functionality uses /etc/rc.conf-like configuration with all of its benefits, but older things need to be migrated or improved upon without causing too much code churn that is hard to test. E.g.:

https://github.com/opnsense/core/issues/412


Cheers,
Franco