Why is init not a session leader? I faced an issue with using CRIU because of that. Adding CRIU folks as well. Error (cr-dump.c:1598): A session leader of 74(1) is outside of its pid namespace
68 0 0:00 lxc-start -n container -f lxc.conf -d -- /init 74 0 0:00 /init On Mon, Jan 5, 2015 at 9:48 AM, Serge Hallyn <serge.hal...@ubuntu.com> wrote: > lcxapi_start calls setsid but not from the task which will become the > container init. > > Quoting beproject criu (beprojectc...@gmail.com): >> Dear LXC Developers, >> Does anybody have any idea why lxc-start executable does not make init the >> session leader, whereas lxcapi_start function does call setsid() >> >> On Sat, Jan 3, 2015 at 11:55 AM, Ashish Bijlani <ashish.bijl...@gmail.com> >> wrote: >> >> > Could you reply to this email and ask LXC developers to help….if anyone >> > has any idea on this. >> > >> > Ask why lxc-start executable does not make init the session leader, >> > whereas lxcapi_start function does call setsid() >> > >> > On Dec 25, 2014, at 10:19 AM, beproject criu <beprojectc...@gmail.com> >> > wrote: >> > >> > Dear LXC Developers, >> > >> > Why init of spawned container is not a session leader?. >> > Can i change the session leader of lxc container using hooks,etc? >> > If yes, how do i do it. >> > >> > Thanks. >> > >> > _______________________________________________ >> > lxc-devel mailing list >> > lxc-devel@lists.linuxcontainers.org >> > http://lists.linuxcontainers.org/listinfo/lxc-devel >> > >> > >> > > >> _______________________________________________ >> lxc-devel mailing list >> lxc-devel@lists.linuxcontainers.org >> http://lists.linuxcontainers.org/listinfo/lxc-devel > > _______________________________________________ > lxc-devel mailing list > lxc-devel@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-devel _______________________________________________ lxc-devel mailing list lxc-devel@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-devel
