Debian bug report logs - #1746
rsh <system> sh -i produces CPU hog

Message received at debian-bugs:

From chiark.chu.cam.ac.uk!ijackson Mon Oct 23 15:54:35 1995
Return-Path: <ijackson@chiark.chu.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t7VlL-000BiMC; Mon, 23 Oct 95 15:54 PDT
Received: from artemis.chu.cam.ac.uk by pixar.com with SMTP id AA25154
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 23 Oct 1995 15:54:05 -0700
Received: from chiark.chu.cam.ac.uk by artemis.chu.cam.ac.uk with smtp
	(Smail3.1.29.1 #33) id m0t7Vl8-0007uaC; Mon, 23 Oct 95 22:54 GMT
Received: by chiark.chu.cam.ac.uk
	id m0t7Vkt-0002YGC
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Mon, 23 Oct 95 22:54 GMT
Message-Id: <m0t7Vkt-0002YGC@chiark.chu.cam.ac.uk>
Date: Mon, 23 Oct 95 22:54 GMT
From: Ian Jackson <ijackson@chiark.chu.cam.ac.uk>
To: Debian bugs submission address <debian-bugs@pixar.com>
Subject: rsh <system> sh -i produces CPU hog

Package: bash
Version: 1.14.4-2

To reproduce:
  rsh <debian-system> sh -i
Or, if from a Debian system with an un-fixed libc, use:
  rsh <debian-system> -- sh -i
(This is bug#911, which started out life with me reporting this as a
problem in netstd, and bug#1685, originally reported against dpkg.)

This will sit and not produce a prompt.  Observe in another session:

$ ps guaxww | grep iwj10
ijackson 12234  0.2  1.1   51  220 pp4 S    22:47   0:00 rsh localhost -l iwj10 -- sh -i
ijackson 12237  0.0  0.8   51  152 pp4 S    22:47   0:00 rsh localhost -l iwj10 -- sh -i
iwj10    12238 78.3  1.9  298  368  ?  R    22:47   0:40 sh -i
iwj10    12260  7.0  2.8  304  536 pp9 S    22:48   0:00 -bash
iwj10    12262  0.0  1.3  112  260 pp9 R    22:48   0:00 ps guaxww
iwj10    12263  0.0  1.3  160  244 pp9 S    22:48   0:00 grep iwj10
$ kill 12238
$ kill 12238
$ kill 12238
$ kill 12238
$ kill 12238
$ kill -9 12238
$ kill -9 12238
kill: (12238) - No such pid
$ 

So, the errant bash process doesn't even exit on SIGTERM.

Ian.