I am in the same boat as Vegar Nilsen. Not being able to do a graceful apache restart is a bummer.
Not an expert in systemd affairs, but if systemd is unable to track PIDs of services it started, doesn't that make it a bug in systemd (or the apache unit file)?
apache2 is run in cgroup /system.slice/apache2.service, and it should not be able to escape from it in any way. So how comes that systemd cannot find/manage these processes after a graceful restart?
I am in the same boat as Vegar Nilsen. Not being able to do a graceful apache restart is a bummer.
Not an expert in systemd affairs, but if systemd is unable to track PIDs of services it started, doesn't that make it a bug in systemd (or the apache unit file)?
apache2 is run in cgroup /system. slice/apache2. service, and it should not be able to escape from it in any way. So how comes that systemd cannot find/manage these processes after a graceful restart?