Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!cuff!evan
From: evan@dmr.com (Evan B. Ross)
Newsgroups: comp.unix.sysv386
Subject: Finally!! CTL-S works on SCO
Message-ID: <1991Apr19.203335.21577@dmr.com>
Date: 19 Apr 91 20:33:35 GMT
Organization: DMR Wellesly, MA
Lines: 57

After much tooth pulling, hair tugging, and bickering with SCO Technical
support, I've finally found a way to make SCO's rlogin and telnet pass
Ctl-S transparently to the remote host.

SCO not only said that this was impossible, they said it was designed to be
that way!! (read the rfc's guys!)

The problem is caused by rlogin and telnet diddling with the stty parameters
once they've been invoked. So I (with help from my colleagues) wrote several
very simple scripts that do the following:

	Learn the ID of the job's tty (or pty)
	Spawn a script in the background that sleeps for 5 seconds,
	  and then changes the tty characteristics.
	Opens an rlogin connection.

This requires three files, the main script, the child script, and a tiny awk
program.

The main script (which I've called sco_rlogin) is:

--
	mytty=`ps | awk -f /usr/local/scobin/ptty.awk`
	/usr/local/scobin/ptty.stty $mytty &
	rlogin $1
--

The child script (ptty.stty) is:

--

	sleep 5 ; stty -ixon -ixoff -ixany <$1

--

And the awk program is:

--
	{
	if(NR==2)
		printf("/dev/tty%s\n",$2)
	}
--

Well, there you have it. I'm sure it could be simplified (putting the awk
program in-line, for instance), but it works as is.

So far in my battle with SCO the score is about Me: 7, SCO: 1.




-- 
  There's sparks a comin' outa' my head!!!

	Evan B. Ross		evan@dmr.com
	DMR, Wellesley MA