On Tue, Oct 13, 2009 at 08:32, Mark Post <[email protected]> wrote: > >>> On 10/13/2009 at 8:45 AM, Thang Pham <[email protected]> wrote: > > I understand that RHEL 5.4 has a terminal server, is there any > > documentation about how to install and use it? > > https://www.ibm.com/developerworks/linux/linux390/documentation_dev.html > which points to > How to Set up a Terminal Server Environment - SC34-2596-00 > > http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26dht00.pdf > >
I've just set this up on a RHEL 5.4 system and it works quite nicely. I'd have done it much sooner, but the doc says kernel 2.6.29 + maint, or 2.6.30 is required. (RHEL is at 2.6.18, so I wasn't in a hurry to investigate further.) Is there a way to globally/persistently change the default terminal identifier when using the ts-shell connect command? I'd have expected to do that in ts-shell.conf I don't use hvc, so to work around this, on the target machines I coded a second iucvtty instance with lnxhvc0 as the expected terminal id. That works fine, but it's a bit misleading and just seems "wrong". :-) I'd also like to turn the pager off when using the list command... Perhaps another option in ts-shell.conf? pager=no, or pager=<path to pager> I miss the command history... it's OK (even desirable) to have that kept for the current ts-shell session only. (Similar to how "terminal" works) How to grant access to the LXTS machine itself? For fun I started iucvtty instances on LXTS and authorized myself to connect to LXTS... it worked... but, as expected, I got a new ts-shell session... Perhaps, ts-shell could check the destination machine, and if it is itself start a shell [1] instead of continuing with an IUCV connection. Securing that becomes the same as securing access to target machines. That way I don't have to create a separate userid on LXTS for the people that support LXTS and target machines, or put another way, LXTS can be treated similarly to other target machines. Overall... very nice. :-) Cheers, Donald Russell [1] Which shell to start? Configured in ts-shell.conf of course. :-) shell=... ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
