> That says nothing about what the child process does.
Correct, but that is as far as I get with my knowledge :-). I've also a
strace with Bash 4.1 patchlevel 9 around this point and that goes as
follows:
...
clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr
I've noticed the same behavior
while it works with the original redhat/cenos (3.2.25) shell it will
not work with 4.2.6
Example:
# vzctl enter 152
will just hang.
Attaching to the bash process within the container shows the following
backtrace:
(gdb) bt
#0 0x00f297f2 in _dl_sysinfo_int80
On 3/4/11 4:50 AM, gnu.bash.bug wrote:
> I've noticed the same behavior
>
> while it works with the original redhat/cenos (3.2.25) shell it will
> not work with 4.2.6
>
> Example:
>
> # vzctl enter 152
> will just hang.
>
> Attaching to the bash process within the container shows the follo
Any hints how to troubleshoot this?
I tried to change the root shell "to /bin/bash -v" but did not get any
more output...seems as as the shell starts but hangs before displaying
the prompt.
The strange thing is that it works while logging in using ssh to the
same container.
//Michael
