Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: Re: lost tty output Message-ID: <CC8HFH.Ey0@veda.is> Date: 23 Aug 93 22:35:27 GMT References: <CC7tKC.Aoz@veda.is> <25b2rf$98m@wzv.win.tue.nl> Organization: Veda Systems, Iceland Lines: 24 guido@gvr.win.tue.nl (Guido van Rooij) writes: >adam@veda.is (Adam David) writes: >>if ping is run from a 'screen' window instead of from an unprotected network >>login. The 'stty -a' settings were identical after losing the output, compared >>to what they were before running the ping. >I just checked hee, but I don't have that behaviour here. pk 0.2.4 + codrv >as well, including some patches of my own. I just got the same behaviour rlogged in to another host (HP-UX 9.x), there was no output available after ^C interrupting 'ping $remote_uphost' from there, again it was a session unprotected by 'screen' on the 386bsd host. BTW, (I forgot to mention) this behaviour does not occur on the virtual consoles, it is only across a network login. Could it be a problem which is compounded by the terminal emulator that I am using on the client machine? I telnetted direct from the client terminal to the HP-UX machine, and the problem did not occur. This is a ping time of around quarter to half a second with 2 packets dropped in the process of interrupting the command (network speed is limited by slip). -- adam@veda.is