On 23/02/12 17:12, Kirill Kolyshkin wrote:
> Using ~. would be problematic since it interferes with e.g. ssh.
>
Hmm, on reflection, I can see "ESC ." possibly causing accidental
escapes when using vi? A reasonably common vi sequence is to insert a
body of text, and then repeat that insert. Wo
Kir,
Thanks for your work on this!
On Fri, Feb 24, 2012 at 12:38:46AM +0400, Kir Kolyshkin wrote:
> See, the problem here is you usually access your node through ssh, and
> if we will use the same sequence than ssh will close.
Not necessarily. The person will need to type ~~. (or ~~~., etc.) t
On 02/23/2012 08:18 PM, Tim Small wrote:
On 23/02/12 14:39, Kir Kolyshkin wrote:
I am glad to announce CT console feature.
Very cool - been on my wish list for a while!
Available in RHEL6-based kernel since 042stab048.1, this feature is
pretty simple to use. Use vzctl attach CTID to attach to
On 23/02/12 14:39, Kir Kolyshkin wrote:
> I am glad to announce CT console feature.
Very cool - been on my wish list for a while!
> Available in RHEL6-based kernel since 042stab048.1, this feature is
> pretty simple to use. Use vzctl attach CTID to attach to this
> container's console, and you wi
I am glad to announce CT console feature.
Available in RHEL6-based kernel since 042stab048.1, this feature is
pretty simple to use. Use vzctl attach CTID to attach to this
container's console, and you will be able to see all the messages CT
init is writing to console, or run getty on it, or an
