Xref: utzoo comp.dcom.lans:1100 comp.protocols.tcp-ip:2675 comp.protocols.misc:238 comp.windows.misc:180 Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!ptsfa!pacbell!att-ih!ihnp4!ho95e!wcs From: wcs@ho95e.ATT.COM (Bill.Stewart.) Newsgroups: comp.dcom.lans,comp.protocols.tcp-ip,comp.protocols.misc,comp.windows.misc Subject: Re: rlogin from windows Message-ID: <2034@ho95e.ATT.COM> Date: 5 Mar 88 00:46:13 GMT References: <707@hadron.UUCP> Reply-To: wcs@ho95e.UUCP (46323-Bill.Stewart.,2G218,x0705,) Organization: AT&T Bell Labs 46133, Holmdel, NJ Lines: 31 Keywords: rlogin, windows, networks, Datakit! In article <707@hadron.UUCP> jsdy@hadron.UUCP (Joseph S. D. Yao) writes: :On a heterogenous (System V / Ultrix) TCP/IP network, several people :use 'rlogin' from windows, and are surprised when the computer on the :far side believes that they have the full complement of lines and :columns. My suggested solution was to add to the third rlogin [....] :Since the System V terminfo uses environment variables $LINES and :$COLUMNS, we could use those on the System V machines; and we'd have :to get the Berkeley machines somehow to modify $TERMCAP based on :$LINES and $COLUMNS. I run into this problem with my AT&T Datakit network and 5620 window terminal. Datakit has two separate remote login equivalents, plus "live" remote exec. For machines with a "real" hardware interface, there's a variable called "DKEXPORT", which is a list of the environment variables you want passed to the remote machine on remote login and remote execution. So I set DKEXPORT="TERM,LINES,COLUMNS,WHATEVER" and the current value of those variables is set in the remote environment. For machines that only have RS-232 connections, you get a "cu" equivalent, with no special support. When I'm talking to one of them, my .profile prints an escape sequence that the terminal program responds to with LINES=xx; COLUMNS=yy; export LINES COLUMNS which is boring but almost always enough, and offeres a csh-variant. Neither of these programs tells the remote system to set the various ioctl modes associated with the windowing terminal, but the most applications look for the environment variables first. -- # Thanks; # Bill Stewart, AT&T Bell Labs 2G218, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs