> I haven't been able to find where in upstart this is happening, but on the > kernel side I can tell that it's due to an open() without > O_NOCTTY.
Upstart does not open /dev/console without O_NOCTTY afaics. Are you sure your kernel debug is showing pid 1 is doing this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1263738 Title: login console 0 in user namespace container is not configured right Status in Upstart: New Status in “linux” package in Ubuntu: Confirmed Status in “lxc” package in Ubuntu: Triaged Status in “linux” source package in Trusty: Confirmed Status in “lxc” source package in Trusty: Triaged Bug description: When you create a container in a private user namespace, when you start the container without the '-d' flag, that console is not properly set up. Logging in gives you -bash: no job control in this shell and hitting ctrl-c reboots the container. Consoles from 'lxc-console -n $container' behave correctly. This may be a kernel issue, as discussed here: http://lists.linuxcontainers.org/pipermail/lxc- devel/2013-October/005843.html so also marking this as affecting the kernel. This can be worked around, but really needs to be fixed before trusty is frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1263738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
