This is likely not lxc-attach's fault. It seems that timeout is sending SIGTTOU to the process it monitors. If you send this to a tty it will stop until it receives a continue signal. So this behaviour is, I'd argue, correct. Newer versions of lxc-attach allocate a tty whenever they can to prevent
The following pull request was submitted through Github.
It can be accessed and reviewed at: https://github.com/lxc/lxd/pull/2833
This e-mail was sent by the LXC bot, direct replies will not reach the author
unless they happen to be subscribed to this list.
=== Description (from pull-request) ===
On Wednesday, 1. February 2017 11:23:35 Thomas Jarosch wrote:
> #
> cat > lxc_hang.sh << EOF
> /usr/bin/timeout 5s /usr/bin/lxc-attach -n amavisd -- /bin/true
> EOF
> chmod a+rx lxc_hang.sh
>
> # works - executed directly
> /usr/bin/timeout 5s /usr/bin/lxc-attach -n amavisd -- /bin
Hey there,
after updating from LXC 1.1.5 to 2.0.7, I found a little regression:
A command executed via lxc-attach suddenly hangs.
I've minimized the test case for a container named "amavisd" to this:
#
cat > lxc_hang.sh << EOF
/usr/bin/timeout 5s /usr/bin/lxc-attach -n amavisd --
