Debian bug report logs -
#1702, boring messages
Message sent to debian-devel@pixar.com:
Subject: Bug#1702: telnet+su root->thermal process
Reply-To: richard@sfere.elmail.co.uk (Richard Kettlewell), debian-bugs@pixar.com
Resent-From: richard@sfere.elmail.co.uk (Richard Kettlewell)
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 18 Oct 1995 18:33:02 GMT
Resent-Message-ID: <debian-bugs-handler.1702.B10181831450@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: bash
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Wed, 18 Oct 1995 18:33:02 GMT
Received: with rfc822 via encapsulated-mail; Wed, 18 Oct 1995 18:31:43 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t5dBJ-000B3PC; Wed, 18 Oct 95 11:25 PDT
Received: from muskogee.elmail.co.uk by pixar.com with SMTP id AA10461
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Wed, 18 Oct 1995 11:25:05 -0700
Received: from sfere.elmail.co.uk ([193.116.29.15]) by muskogee.elmail.co.uk
with smtp id <m0t5dBI-0003A1C@muskogee.elmail.co.uk>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 18 Oct 95 19:25 BST
Received: by sfere.elmail.co.uk
id <m0t5dCg-0002R8C@sfere.elmail.co.uk>
(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 18 Oct 95 19:27 BST
From: richard@sfere.elmail.co.uk (Richard Kettlewell)
Message-Id: <8MxkrSOM2@sfere.elmail.co.uk>
Date: Wed, 18 Oct 95 19:27:02 +0100 (BST)
To: debian-bugs@pixar.com
In-Reply-To: <Pine.LNX.3.91.951019004517.16324B-100000@spark.net.hk>
References: <Pine.LNX.3.91.951019004517.16324B-100000@spark.net.hk>
Package: bash
Version: 1.14.4-2
william@spark.net.hk writes:
>Hi debian ppl,
>
> I just wonder if anybody has this problem too 'cos my debian is
>upgrading from old debian packages.
>
>telnet localhost
><login and passwd checking>
>su root
>more /etc/inetd.conf (any long text file will do)
>press ctrl-] and quit to terminate the telnet session
>now...there is a crazy bash running there and will eat up all the cpu
>time shortly!
>
> I'm looking for a quick fix 'cos I always need to telnet to
>server for my works.
Does the same to me.
The quick fix is ``don't do that then'' - quit `more' by hitting `q',
close the session by terminating bash (hit ^D or type `exit') rather
than chopping off the telnet connection from your end.
I've had a prod around but I still don't understand what is going on.
At first I thought that it was just that the rogue bash was ignoring
SIGHUP or something; however manually SIGHUPing it (instead of closing
the telnet connection) contradicts this.
It may be that the bug is in telnetd rather than bash, but the fact
that bash starts eating CPU when it loses its tty is a bug in itself.
ttfn/rjk
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: richard@sfere.elmail.co.uk (Richard Kettlewell)
Subject: Bug#1702: Acknowledgement (was: telnet+su root->thermal process)
In-Reply-To: <8MxkrSOM2@sfere.elmail.co.uk>
References: <8MxkrSOM2@sfere.elmail.co.uk>
Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1702" or "Re: Bug#1702" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Message sent to debian-devel@pixar.com:
Subject: Bug#1702: telnet+su root->thermal process
Reply-To: tobias@et-inf.fho-emden.de, debian-bugs@pixar.com
Resent-From: "Peter Tobias" <tobias@server.et-inf.fho-emden.de>
Resent-To: debian-devel@pixar.com
Resent-Date: Thu, 19 Oct 1995 10:18:01 GMT
Resent-Message-ID: <debian-bugs-handler.1702.B10191009210@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: bash
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Thu, 19 Oct 1995 10:18:01 GMT
Received: with rfc822 via encapsulated-mail; Thu, 19 Oct 1995 10:09:19 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0t5rtI-000BAoC; Thu, 19 Oct 95 03:08 PDT
Received: from server.et-inf.fho-emden.de by pixar.com with SMTP id AA11210
(5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Thu, 19 Oct 1995 03:07:28 -0700
Received: by server.et-inf.fho-emden.de (5.65/DEC-Ultrix/4.3)
id AA20425; Thu, 19 Oct 1995 10:58:01 +0100
Message-Id: <9510190958.AA20425@server.et-inf.fho-emden.de>
To: richard@sfere.elmail.co.uk, debian-bugs@Pixar.com
Date: Thu, 19 Oct 1995 10:58:01 +0100 (MET)
From: "Peter Tobias" <tobias@server.et-inf.fho-emden.de>
In-Reply-To: <8MxkrSOM2@sfere.elmail.co.uk> from "Richard Kettlewell" at Oct 18, 95 07:27:02 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Content-Length: 767
Richard Kettlewell wrote:
> Package: bash
> Version: 1.14.4-2
[...]
> I've had a prod around but I still don't understand what is going on.
> At first I thought that it was just that the rogue bash was ignoring
> SIGHUP or something; however manually SIGHUPing it (instead of closing
> the telnet connection) contradicts this.
>
> It may be that the bug is in telnetd rather than bash, but the fact
> that bash starts eating CPU when it loses its tty is a bug in itself.
I just tried it with the csh and it works.
Peter
--
Peter Tobias EMail:
Fachhochschule Ostfriesland tobias@et-inf.fho-emden.de
Fachbereich Elektrotechnik und Informatik tobias@perseus.fho-emden.de
Constantiaplatz 4, 26723 Emden, Germany
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: tobias@et-inf.fho-emden.de
Subject: Bug#1702: Info received (was Bug#1702: telnet+su root->thermal process)
In-Reply-To: <9510190958.AA20425@server.et-inf.fho-emden.de>
References: <9510190958.AA20425@server.et-inf.fho-emden.de>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developers to
accompany the original report.
If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#1702" or "Re: Bug#1702" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism