On Fri, 2011-02-04 at 14:27 +0300, Kir Kolyshkin wrote:
> On 02/04/2011 01:44 PM, Bastian Blank wrote:
> > On Fri, Feb 04, 2011 at 11:06:38AM +0300, Kir Kolyshkin wrote:
> >>> Many OpenVZ containers are still likely to require the legacy pty option
> >>> in
> >>> the kernel in order for "vzctl ent
Given the assumptions that containers run different distros,
including some older ones, this option is needed.
...
Still, my opinion is the feature is from "good to have" department
rather than from "absolutely required".
Hello Kir, thanks for the response.
I have been using VZ since 2004 and
On 02/04/2011 01:44 PM, Bastian Blank wrote:
On Fri, Feb 04, 2011 at 11:06:38AM +0300, Kir Kolyshkin wrote:
Many OpenVZ containers are still likely to require the legacy pty option in
the kernel in order for "vzctl enter" or "ssh" to work.
Please explain why. ssh always use openpty, which works
On Fri, Feb 04, 2011 at 11:06:38AM +0300, Kir Kolyshkin wrote:
> >Many OpenVZ containers are still likely to require the legacy pty option in
> >the kernel in order for "vzctl enter" or "ssh" to work.
Please explain why. ssh always use openpty, which works fine with
devpts.
> >I can work around
That makes total sense from my perspective, so I second the request.
--
sent from mobile
Mark Lehrer wrote:
>Many OpenVZ containers are still likely to require the legacy pty option in
>the kernel in order for "vzctl enter" or "ssh" to work.
>
>I can work around it for my environment, but a lo
Many OpenVZ containers are still likely to require the legacy pty option in
the kernel in order for "vzctl enter" or "ssh" to work.
I can work around it for my environment, but a lot of people will have
difficulty if the CONFIG_LEGACY_PTYS option isn't set in the default kernel.
Would it be po
6 matches
Mail list logo
