What? Why did you effectively remove both `apachectl graceful` and `systemctl reload apache2` and not leave any alternative?
We're using this pretty much every day to avoid downtime on our mod_security web filter, since it takes a while to do a full restart of Apache with 600+ vhosts: vegar@webwash02:~$ sudo apache2ctl -S | grep -c namevhost 667 vegar@webwash02:/etc/apache2/sites-enabled$ sudo apachectl -t Syntax OK vegar@webwash02:/etc/apache2/sites-enabled$ sudo apachectl graceful Invoking 'systemctl restart apache2'. Use 'systemctl status apache2' for more info. I definitely did not expect a change like this to just be implemented in an LTS version with no notice in security-announce. So every single time we add a new vhost to our web filter, we'll have to do something like this instead of just running `sudo apachectl graceful`: vegar@webwash02:~$ sudo apachectl -t Syntax OK vegar@webwash02:~$ systemctl status apache2 | grep "Main PID" Main PID: 97192 (apache2) vegar@webwash02:~$ sudo kill -HUP 97192 This definitely makes things easier, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
