Hi! For those who have not noticed yet...
A new version of vzctl was released which fixes this issue: http://bugzilla.openvz.org/show_bug.cgi?id=1812#c7 Thanks for all help! Michael On 15 mar, 17:03, Chet Ramey <chet.ra...@case.edu> wrote: > > > So vzctl is running bash in a pty and talking to it that way? > > > For the exact details I'll point to the OpenVZ guys :-). It is an OS > > virtualization patch for the kernel. With it you can run virtual servers > > which are isolated from each other. > > The answer to my question was "yes." > > > What exactly do you want. A full strace report? > > That's what I got, and the strace points the finger at vzctl. It looks > like a bug in vzctl that was masked by bash-4.1 and previous versions. > > > I'm trying to find the difference between 4.1.9 and 4.2.0 which causes > > this behavior, but that is not simple because I don't know the order and > > which differences I must combine. So this process will take a while... > > The difference looks to be that bash-4.1 closed fds 3-20 at startup, and > bash-4.2 sets open fds in that range to close-on-exec. vzctl is careless > with its file descriptors, and bash not closing them results in its > controlling terminal getting messed up. > > Michael Kalisz opened a bug report with the openvz group. > > Chet > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
