Xref: utzoo comp.sys.att:8502 comp.unix.wizards:20214
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucsdhub!celit!fpssun!nosun!ohsuhcx!bj
From: bj@ohsuhcx.ohsu.edu (Bill Jackson)
Newsgroups: comp.sys.att,comp.unix.wizards
Subject: Works on /dev/tty*; not on /dev/slan*
Keywords: starlan tcpip dev
Message-ID: <321@ohsuhcx.ohsu.edu>
Date: 18 Jan 90 00:32:08 GMT
Organization: Oregon Health Sciences University, Portland
Lines: 18

I have a strange problem (aren't they all 8-).
An application program, which works fine on a direct connected terminal or a
terminal coming in over a TCP/IP lan connection, fails miserably on a StarLan
connection.  In fact it stalls completely; no output, seemingly no terminal
input - only way out is to bail out completely and come back in.

I spent some time looking at differences in the stty settings and enviroment
variables and convinced myself there was nothing fundamentaly wrong there so
I went on to try silly things and guess what?  If I start the application
program the normal way (which is using a PC terminal, TE Works/LAN terminal
emulator via StarLan to a 3B2), I get the expected result (i.e. nothing!)
If I start the application and pipe output to tee /dev/null, it works fine!

Does anbody have any ideas as to what is going on here?
-- 
William Jackson               University Systems & Computing, Gaines Hall #113
Oregon Health Sciences University, 3181 S.W. Sam Jackson Park Rd, Portland, OR 
(503) 279 4535     bj@ohsu.edu    {nosun, tektronix, ogicse, uunet}!ohsuhcx!bj