Mark Hatle 2305c0038d pseudo: Fix problem where pseudo could kill a container init ... In a heavily loaded container, the child process might not started before the parent process had terminated. The child process attempts to signal the parent with SIGUSR1. If the parent had terminated, the parent becomes PID 1, which is generally init. When it signaled pid 1, it caused the docker mini-init to terminate. This doesn't happen in a traditional system, as systemd/sysvinit is protected to only root users can signal it. [YOCTO #10324] (From OE-Core rev: f6f13b049e8683d2a2af3e120ba979b58f9a7d9a) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2016-09-24 07:30:10 +01:00
..
files	pseudo: Fix problem where pseudo could kill a container init	2016-09-24 07:30:10 +01:00
pseudo.inc	pseudo: Upgrade to 1.8.1	2016-07-08 10:50:18 +01:00
pseudo_1.8.1.bb	pseudo: Fix problem where pseudo could kill a container init	2016-09-24 07:30:10 +01:00
pseudo_git.bb	pseudo: Fix problem where pseudo could kill a container init	2016-09-24 07:30:10 +01:00