Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!howland.reston.ans.net!noc.near.net!lobster.sid.mcet.edu!lobster.sid.mcet.edu!johnj From: johnj@lobster.sid.mcet.edu (John Jackson) Newsgroups: comp.os.386bsd.bugs Subject: Telnet terminal problems w/386BSD Date: 6 May 1993 04:57:16 GMT Organization: MCET - Massachusetts Corporation for Educational Telecommunications Lines: 42 Message-ID: <1sa5rc$9r9@lobster.sid.mcet.edu> NNTP-Posting-Host: lobster.sid.mcet.edu X-Newsreader: TIN [version 1.1 PL8] Hi: I have 386BSD 0.1 patch level 0.2.1. Telnetting in to the 386BSD box can be dicey. If I'm on a DOS PC and I telnet to the 386BSD host using NCSA telnet (latest version) over ODIPKT 2.1 I have a problem running emacs if I am using the tcsh that came with 386BSD as my shell. Basically, as soon as I execute emacs I get a non-stop stream of new lines to my NCSA telnet screen. I must ungracefully exit NCSA telnet and start over again, being careful to use vi instead. I forget if this happens while using just csh. However, I know that if I do use csh using talk causes the same condition when I terminate it. BTW, I must termnate it by logging in on another wwindow and killing the talk process. Neither myself or the person I am in talk with (even if they are on another machine somewhere else) can use Ctrl-C to terminate talk. If I use NCSA telnet 2.5 via a Macintosh & MacTCP to get on my 386BSD box emacs and most things work fine. However, in that scenario, the 386BSD host doesn't accept Ctrl-C to kill a ping process - I must use Ctrl-Y instead Also, Ctrl-Z isn't recognized by the shell to suspend a program. I do know that these keys are working though because if I telnet out to another system from there Ctrl-C and Z work like their supposed to. Another bizzare thing that happens is when I telnet from the 386BSD box to the management port of my Xyplex Network 9000 terminal server. Every prompt that the Xyplex terminal server puts on my screen has a ^J appended to it. I must backspace it away before entering a command to the terminal server or it is accepted by the terminal server as input. Finally, if I have a remote user come in via a modem via the Xyplex terminal server into the 386BSD box AND that user disconnects in the middle of emacs without logging out properly it somehow messes up the pty that they were connect to. The next Mac/NCSA telnet Mac 2.5 user who telnets in to the 386BSD box directly from our LAN and who gets that pty finds that they get a login prompt and can enter their login name but after they hit a carrige return the connection hangs. The only way to fix such a sick pty is to either login in to it via a DOS machine and NCSA telnet and log out (this sometimes works) or to reboot the 386BSD box. Have I given enough useful description of the problems that I'm having? Overall our 386BSD system is way cool. It is our everything machine - Internet gateway via a 14.4 v.42 cslip line, news and email server and a few other things. I'm not sure if the NCSA telnet programs are flaky or 386BSD is. I suspect 386BSD because I wouldn't think that flaky telnet clients should cause lasting effects on the 386BSD's operation for subsequent connections. Anyone else notice any of the above problems/have any suggested fixes? -John