Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site iuvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!iubugs!iuvax!wagle
From: wagle@iuvax.UUCP
Newsgroups: net.news
Subject: Potential LineEater
Message-ID: <2800010@iuvax.UUCP>
Date: Fri, 17-Jan-86 11:51:00 EST
Article-I.D.: iuvax.2800010
Posted: Fri Jan 17 11:51:00 1986
Date-Received: Tue, 21-Jan-86 01:19:49 EST
Lines: 23
Nf-ID: #N:iuvax:2800010:000:1015
Nf-From: iuvax!wagle    Jan 17 11:51:00 1986


[ I'm NOT anything resembling a net-news wizard ]

  I've been noticing reports of line eater bugs, and it reminded me of a
problem with "tip" (BSD4.2 version of "cu") that I had a couple of months
ago.

  I would use "tip" to link to a system called "sytek" (if you don't know
what "sytek" is, you probably don't need to worry about this note) to link
to a VAX/VMS system.  I had borrowed somebodies ".tiprc" file that had
settings that confused "tip" and/or "sytek" into dropping LOTS of characters
the remote machine was sending at me, particularly when I would X-OFF to
pause the output so I could look at it.

  So I guess what I'm driving at is that if a node to node connection is done
via sytek at some point, that connection may bear some careful looking at.

  I can give more careful details via e-mail to anybody who needs it.

Perry Wagle, Indiana University, Bloomington Indiana.
...!ihnp4!inuxc!iuvax!wagle	(USENET) (avoid ihnp4 if possible)
wagle@indiana			(CSNET)
wagle%indiana@csnet-relay	(ARPA)