This has been my experience with systemd and other daemons, if systemd
(systemctl) wasn't used to make the change (maybe 'service' was used or 'kill')
then systemd erroneously assumes that nothing has changed and doesn't check
reality.
From: ubuntu-server on
Hi there,
On Tue, Jul 23, 2019 at 8:50 AM Bill Parker wrote:
>
> What are the pros/cons of using
>
> apache2ctl stop|start|restart|etc
>
> instead of
>
> systemctl start|stop|restart|etc apache2.service
I recall two recent bugs related to your question:
"systemd unable to detect running apache
What are the pros/cons of using
apache2ctl stop|start|restart|etc
instead of
systemctl start|stop|restart|etc apache2.service
commands? I'm more used to using apache2ctl myself (well, apachectl as
was!) but is this just a (stolen from perl) example of "there's more than
one way to do it"?
--
