start: setsid in init task as well

If we don't do this, we'll leak the parent's session id to the container, which maybe doesn't matter, but it still seems better to set it anyway. Also, it breaks CRIU for containers that don't call setsid themselves. Signed-off-by: Tycho Andersen <tycho.andersen@canonical.com>

start: setsid in init task as well
8c9a7665 · Tycho Andersen · fa79f0a4 · 8c9a7665
Commit 8c9a7665 authored Feb 25, 2016 by Tycho Andersen
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 0 deletions

start.c src/lxc/start.c +2 -0

No files found.
--- a/src/lxc/start.c
+++ b/src/lxc/start.c
@@ -851,6 +851,8 @@ static int do_start(void *data)
 		goto out_warn_father;
 	}

+	setsid();
+
 	/* after this call, we are in error because this
 	 * ops should not return as it execs */
 	handler->ops->start(handler, handler->data);