Hi again Now I have found what the NDELAY mode is. What happens is that when it tries to read from stdin it get the error code EWOULDBLOCK. Then it looks like it turns off non-blocking mode.
This probably explains the situation and it also explains the error message. The resource is _temporarily_ unavailable. Bash should really retry as that is what the error code tells. There is an interesting discussion here: http://lists.busybox.net/pipermail/busybox/2009-November/070914.html But still vzctl should probably not do as it do as it can result in strange behaviour on the shell afterwards. Best regards, // Ola On Sun, Aug 21, 2011 at 09:56:51PM +0200, Daniel Alder wrote: > Hi Ola > > >> Yes, please. Forward it upstream > > > > I'll do that. > > Thanks > > >>> vzctl enter 201 --exec exit ; read a >>> (does not work) >>> >>> vs. >>> >>> vzctl enter 201 --exec exit >>> read a >>> (works) >> >> This is really really interesting. Maybe this is not a vzctl bug after >> all. Maybe it is a bash bug... >> >> Do you know if the same thing happens if you run dash? I have not >> checked myself. > > As I wrote in my first mail, the effect is the same in dash, only a > message is printed aditionally: > > --- > dash > # vzctl enter 222 --exec exit ; read a > entered into CT 222 > exit > root@durin:/# exit > logout > exited from CT 222 > sh: turning off NDELAY mode > # > --- > > ... but I wasn't able to find out more (useful) information about this > message > > > > Daniel > -- --------------------- Ola Lundqvist --------------------------- / [email protected] Annebergsslingan 37 \ | [email protected] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
