Bug#1746: rsh <system> sh -i produces CPU hog

[Ian Jackson <ijackson@chiark.chu.cam.ac.uk>]

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.