Jarrod,I seem to use Ctrl-E c f, to force connection, especially of there is a lurking console running, whether a zombie process or on another screen session. I have also used this, when supporting a customer, who's had the connection already made, and therefore I am automatically in SPY mode; so Ctrl-E c f, resolved that for me.
I don't think I've that many requests wrt shared read/write access to the console; from my aspect, just create some new escape sequences, and I guess we'll go with them
regards, Arif Ali Senior HPC Technical Architect OCF plc Tel: +44 (0)114 257 2200 Mob: +44 (0)7970 148 122 Fax: +44 (0)114 257 0022 Web: www.ocf.co.uk <http://www.ocf.co.uk> Blog: blog.ocf.co.uk <http://blog.ocf.co.uk> Twitter: @ocfplc <http://twitter.com/#%21/ocfplc>OCF plc is a company registered in England and Wales. Registered number 4132533, VAT number GB 780 6803 14. Registered office address: OCF plc, 5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield, S35 2PG.
This message is private and confidential. If you have received this message in error, please notify us and remove it from your system.
On 07/04/14 14:51, Jarrod B Johnson wrote:
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.
<<attachment: aali.vcf>>
------------------------------------------------------------------------------ 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
