Lennart Poettering <[email protected]> writes: > On Mon, 27.07.15 20:29, Ben Gamari ([email protected]) wrote: > >> Lennart Poettering <[email protected]> writes: >> >> > On Fri, 17.07.15 12:23, Ben Gamari ([email protected]) wrote: >> > >> snip >> >> >> Why might this be the case? Does nspawn prevent the process from getting >> >> a controlling tty? >> > >> > The pty setup code changed in nspawn evrsions, hence it is important >> > to say which version you are running? >> > >> Ahh, of course. This is a Debian sid machine, so systemd 221. > > That's pretty recent. Any chance you can strace this, checking where > this "/7" file comes from? > Sure.
This Gist [1] is the output from
$ strace -f -ohi systemd-nspawn --personality=x86-64 -D$MY_CHROOT
and running `ls /proc/self/fd -lh` in the resulting shell. This
produced,
$ ls /proc/self/fd -lh
total 0
lrwx------ 1 root root 64 Jul 27 15:02 0 -> /8
lrwx------ 1 root root 64 Jul 27 15:02 1 -> /8
lrwx------ 1 root root 64 Jul 27 15:02 2 -> /8
lr-x------ 1 root root 64 Jul 27 15:02 3 -> /proc/13/fd
Where the links to /8 were broken.
Cheers,
- Ben
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
