So in the new console server, thus far all the client currently supports
is:
ctrl-e, c, ? (help)
ctrl-e, c, . (disconnect console)
I'm going to be adding:
ctrl-e, c, o (reconnect console, note that it already automatically
detects and corrects most situations that I employed ctrl-e, c, o to fixup
today, and that it accelerates fixup of an unconnected session
automatically on client connect)
ctrl-e, c, l, 0 (send break)
Already today, it automatically does something analagous to ctrl-e, c, p on
connection without user request, though I could add it as an explicit
command.
FWIW, the default behavior is currently all clients get write access. I
recall at least one person requesting the current behavior, but was
wondering how many of the following server-enforced modes would be desired:
shared (many can read and write)
exclusive-write (many can see, only one can write at a time)
exclusive-full (only one can read or write to a console at a given time,
buffered replay would be cleared on close of a client session)
Given that, what would be good escape sequences to represent requesting an
write-exclusive or full-exclusive session?
More generally, any other sequences that are very popular or else would
people prefer a scheme different from the conserver approach? I personally
have difficultly with the ubiquitous '~' scheme and find it somewhat handy
to not have to think how many ssh sessions I might have nested.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees_APR
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
