Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!convex!convex!cs.utexas.edu!howland.reston.ans.net!gatech!udel!MathWorks.Com!yeshua.marcam.com!charnel!xmission!u.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (Terry Lambert) Newsgroups: comp.unix.bsd Subject: Re: Problems with telnet and CF/LF Date: 24 Feb 1994 07:20:06 GMT Organization: Weber State University, Ogden, UT Lines: 33 Message-ID: <2khkf6$pdu@u.cc.utah.edu> References: <2kgjt6$3tf@labs2.etf.hr> NNTP-Posting-Host: cs.weber.edu In article <2kgjt6$3tf@labs2.etf.hr> ssasa@zems.etf.hr (Sasa Skevin(RT4.g.) writes: > I got a big problem. I have make a service (gopher)that is available via >telnet to port ( i.e. telnet srcm1.zems.etf.hr 4321 ). >The program is writen in the way that when the key is pressed, then >follows the action imediatly (there is no need to wait for pressing ENTER). >But this isn't working properly , it is expected from the user to >press ENTER after pressing a key. >Is any solution for this ? >(i have use curses.h nodelay(), cbreak(), but without results ... ) The problem you are having results from your gopher daemon expecting to be connected to by telnet, and then not correctly performing the expected telnet option negotiation. The cannonical soloution is to write the gopher daemon correctly so that it negotiates its options according to the RFC's (many MUD/MUSH/MUCK/etc. programs have the same deficiency). Or you could compile a gopher client that was just as dumb as the gopherd about option negotiation. Or you could explicitly unset linemode on your telnet. Consider yourself lucky -- you will not end up with a packet per keystroke on other dumb daemons which can't intelligently negotiate line mode; your telnet's default saves you from this. 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.