Re: [PLUG] Apache2 weird problem

[Rich Freeman <r-plug@thefreemanclan.net>]

On Fri, Jan 29, 2016 at 11:17 AM, Rachel Rawlings <rachelneko@gmail.com> wrote:
>
> The apache daemon is normally taken care of by apachectl, as Keith said above.
>
> Look in /etc/init.d for your server control script (apache2, iirc, for Ubuntu) and do
>
> $ sudo service apache2 status
> $ sudo service apache2 configtest
>

FWIW, on Gentoo apache2 is launched directly by systemd/openrc:
[Unit]
Description=The Apache HTTP Server
After=network.target remote-fs.target nss-lookup.target

[Service]
EnvironmentFile=/etc/conf.d/apache2
ExecStart=/usr/sbin/apache2 $APACHE2_OPTS -DFOREGROUND
ExecReload=/usr/sbin/apache2 $APACHE2_OPTS -k graceful
ExecStop=/usr/sbin/apache2 $APACHE2_OPTS -k graceful-stop

You might be able to get it to work with apache2ctl, but at least with
systemd you want a daemon to either run in the foreground (which is
better from a logging perspective), or to fork its main process and
die.  SystemD wants to know what the main PID is so that it can
monitor it/etc.

I don't think anything bad would happen if you used apache2ctl, though
if you had systemd set up to auto-restart apache and you stopped it
with apache2ctl then unless it was systemd-aware it would just get
restarted automatically.

-- 
Rich
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug