From evanc@synapse.net  Sat Nov 15 06:45:35 1997
Received: from piano.synapse.net (piano.synapse.net [199.84.54.19])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA07030
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 15 Nov 1997 06:45:33 -0800 (PST)
          (envelope-from evanc@synapse.net)
Received: (qmail 26570 invoked by uid 0); 15 Nov 1997 14:45:31 -0000
Message-Id: <19971115144531.26569.qmail@piano.synapse.net>
Date: 15 Nov 1997 14:45:31 -0000
From: evanc@synapse.net
To: FreeBSD-gnats-submit@freebsd.org
Cc: evanc@synapse.net
Subject: Closing xterm leaves /bin/sh sucking 100% CPU
X-Send-Pr-Version: 3.2

>Number:         5053
>Category:       bin
>Synopsis:       Closing xterm leaves /bin/sh sucking 100% CPU
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    steve
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 15 06:50:02 PST 1997
>Closed-Date:    Sun Dec 28 12:14:27 PST 1997
>Last-Modified:  Sun Dec 28 12:16:31 PST 1997
>Originator:     Evan Champion
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

	

>Description:

	Not closing a telnet/rlogin properly does not close /bin/sh.
	/bin/sh starts sucking 100% CPU.

>How-To-Repeat:

	use X on client.
	rlogin/telnet to server.
	kill xterm on client without logging out from server.

	The /bin/sh on the server does not close, and it starts
	sucking 100% CPU.

	This is absolutely reproducable.

>Fix:
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Dec 28 12:14:27 PST 1997 
State-Changed-Why:  
The originator attributes this to using the Kerberos 5 
rlogind.  Switching to using ssh has solved the problem. 
Maybe our resident Kerberos expert would like to look into 
this one further? 
>Unformatted:
