Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!math.fu-berlin.de!news From: u9126619@athmail1.causeway.qub.ac.uk Subject: Terminals on COM* serial ports not handshaking correctly Message-ID: <I4SGBH6I@math.fu-berlin.de> Sender: news@math.fu-berlin.de (Math Department) Nntp-Posting-Host: ash46.causeway.qub.ac.uk Organization: Free University of Berlin, Germany Date: Mon, 30 Aug 1993 11:05:31 GMT Lines: 34 I have a real VT220, a real VT105 and a emulated VT52 connected to the ordinary serial ports of my PC (a multi-io IDE controller). I've put them in the ttys database like so tty01 "/usr/libexec/getty std.9600" vt100 on secure #vt100 tty01 is a simbolic link to com1 etc I can login and use the terminals ok until.... Say I cat a long file then press HOLD then type some letters .. the display stops as it should then I get lots of backwards question marks indicating a buffer offerflow! If there is a heavy load on the sytem I don't need to do this to provoke this behaviour it happens all the time..an it is very irriating! Ok..I have discovered that putting stty -ixany solves the problem. Well not quite! Thats ok until you use a program like script or telnet which uses a device like ttyp0 where ixany is on again! Question is...has anybody seen this before and how do you fix it! And/or...Where does the system get its initial settings for the stty values when it initializes a terminal device...Is it termcap? I can't see anything in it that would suggest any settings for the iflags? (Oh yes the funny thing is that my Atari ST emulating a VT52 works ok with ixany set???) ------------------------------------------------------------------------------ Please send anything of help to u9126619@athmail1.causeway.qub.ac.uk or Post your reply to this newsgroup!