NetBSD Problem Report #10763

Received: (qmail 360 invoked from network); 5 Aug 2000 09:10:31 -0000
Message-Id: <200008050908.e7598NU01058@t37-112.wrs.com>
Date: Sat, 5 Aug 2000 02:08:23 -0700 (PDT)
From: toddpw@best.com
Reply-To: toddpw@best.com
To: gnats-bugs@gnats.netbsd.org
Subject: telnet session does not act on interrupt characters.
X-Send-Pr-Version: 3.95

>Number:         10763
>Category:       bin
>Synopsis:       telnet session does not act on interrupt characters.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 05 09:11:00 +0000 2000
>Closed-Date:    
>Last-Modified:  Fri Aug 11 08:56:00 +0000 2000
>Originator:     Todd Whitesel
>Release:        1.5_ALPHA
>Organization:
	NetBSD (developer)
>Environment:
	machines with telnetd enabled.
System: NetBSD t37-112.wrs.com 1.5_ALPHA NetBSD 1.5_ALPHA (GENERIC) #0: Thu Jul 27 21:19:54 PDT 2000 toddpw@t37-112.wrs.com:/usr/toddpw/rnetbsd-1-5/src/sys/arch/sparc/compile/GENERIC sparc


>Description:
	When I enable telnetd on a 1.5_ALPHA or 1.5C system and login to them,
	interrupt characters like ^C and ^Z are echoed as such but not
	acted upon. ^D (eof) is recognized however.
>How-To-Repeat:
	enable telnetd on a 1.5_ALPHA or 1.5C system.
	telnet in.
	run cat, and try to ^C or ^Z it. watch it echo but ignore you.
>Fix:
	Workaround: stty -extproc.
	1.4.1 shows extproc set in a telnet login, but does not have problems.
	1.4.2 also has extproc set, and exhibits a muted form of the problem
	(it doesn't print a shell prompt immediately, not sure if it has merely
	missed the prompt or if something doesn't happen until I hit return).
>Release-Note:
>Audit-Trail:

From: Todd Whitesel <toddpw@best.com>
To: netbsd-bugs@netbsd.org
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: bin/10763: telnet session does not act on interrupt characters.
Date: Fri, 11 Aug 2000 01:55:20 -0700 (PDT)

 > > PR bin/10763 can be closed.
 > > 
 > > 1.5_ALPHA from August 5 doesn't exhibit the bug any more.

 ... but -rnetbsd-1-5 -D 20000809-UTC does exhibit the 1.4.2 semi-busted
 behavior:

 You can control-c out of 'cat' but it doesn't give you a shell prompt
 immediately. You can type stuff but shell editing is not available,
 however once you hit return the shell grabs control back and prints a
 prompt. After that everything is ok.

 Investigation continues...

 Todd Whitesel
 toddpw @ best.com
>Unformatted:

Home	PR Database Search