On Wed, Apr 1, 2015 at 1:55 AM, Marc Joliet <mar...@gmx.de> wrote: > > Am Tue, 31 Mar 2015 20:05:50 -0600 > schrieb Canek Peláez Valdés <can...@gmail.com>: > > [...] > > With systemd you don't need this, since it can track the real state of its > > services thanks to cgroups. And kill *really* kills all the processes > > associated to a service, something that OpenRC, by design, cannot do. > [...] > > I wonder if that's accurate. I know that OpenRC also uses cgroups for grouping > services, but how much does it actually exploit them?
According to [1]: """ # If you have cgroups turned on in your kernel, this switch controls # whether or not a group for each controller is mounted under # /sys/fs/cgroup. [...] # Set this to YES if yu want all of the processes in a service's cgroup # killed when the service is stopped or restarted. # This should not be set globally because it kills all of the service's # child processes, and most of the time this is undesirable. Please set # it in /etc/conf.d/<service>. # To perform this cleanup manually for a stopped service, you can # execute cgroup_cleanup with /etc/init.d/<service> cgroup_cleanup or # rc-service <service> cgroup_cleanup. # rc_cgroup_cleanup="NO" """ So it's available if you have cgroups turned on, and then you need to set it up globally (which is not recommended), or by service. That wasn't available when I stopped using OpenRC; but then again, that was almost five years ago. Is nice to see OpenRC catching up to systemd. Regards. [1] https://github.com/OpenRC/openrc/blob/master/etc/rc.conf.Linux -- Canek Peláez Valdés Profesor de asignatura, Facultad de Ciencias Universidad Nacional Autónoma de México
