On Tue, Jul 19, 2011 at 4:42 PM, Juliusz Chroboczek <j...@pps.jussieu.fr> wrote: >> Not rocket science about ipc only a loop and two signal to catch: >> - get SIGING: respawn systemd >> - get SIGUSR2: spawn a sulogin shell >> - check if systemd child die, respawn it if needed (rate limited) >> >> All the funky stuff is done by a child of init. > > Hmm.... If you want to support forking daemons, you'll also want > a protocol to signal the child that a monitored process has exited, > won't you?
No, it is the same problem with systemV init of systemd. Forking daemon are reparented to init and we do not know if exit is genuine or not. It seems this problem (double fork) is the basement of using cgroup under systemd ;) Bastien -- 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/CAE2SPAbAd3ZxghLm+UCb-zWXA6ZZdp8btJ=4x4ep66omp1SK=w...@mail.gmail.com
