Dave Hansen <hansendc@xxxxxxxxxx> writes: > On Thu, 2007-03-22 at 09:33 -0500, Serge E. Hallyn wrote: >> >> >> I still prefer that we forego that kthread, and just work toward >> allowing pid1 to exit. Really I think the crufty /proc/<pid> handling >> is the only reason we were going to punt on that for now. > > It's everything _but_ the /proc/<pid> stuff. /proc/{mem,cpu}info and > friends are the ones suspiciously tied to pid 1. The files and directories affected by the oddity you spotted are: /proc/ /proc/self /proc/<pid> That is the complete list. Only /proc/self and /proc/<pid> Actually test for the presence of pid == 1. Eric _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers