]] Scott James Remnant | I investigated using cgroups in Upstart a while back, and hit the exact | same issue. There are two obvious solutions: | | - allow a process to escape its cgroup (kernel patch); this is | completely insane, since cgroups are primarily used for security | containers, system policies, etc. Being able to escape your | container would be a Bad Thing
Or just have per-user cgroups that a process is moved into when logging in, see libpam-cgroup for something that does this. In addition, killing all members in a cgroup when a service goes down is optional, not mandatory, so the tty would be usable just fine. [...] | Also note that Kay's assertion that there's no way to know all the | processes you need to kill is incorrect. UNIX solved this decades ago | with process groups. I believe the problem is that processes can escape and change their process group. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ocgiajgt....@qurzaw.linpro.no
