Debian bug report logs - #1624 , boring messages ----------------------------------------------------------------------- Message sent to debian-devel@pixar.com: Subject: Bug#1624: thermal run away problem Reply-To: william , debian-bugs@pixar.com Resent-From: william Resent-To: debian-devel@pixar.com Resent-Date: Tue, 10 Oct 1995 06:18:01 GMT Resent-Message-ID: Resent-Sender: iwj10@cus.cam.ac.uk X-Debian-PR-Package: X-Debian-PR-Keywords: Received: via spool for debian-bugs; Tue, 10 Oct 1995 06:18:01 GMT Received: with rfc822 via encapsulated-mail; Tue, 10 Oct 1995 06:04:14 GMT Received: from pixar.com by mongo.pixar.com with smtp (Smail3.1.28.1 #15) id m0t2XmR-000BUaC; Mon, 9 Oct 95 23:03 PDT Received: from is2.spark.net.hk (spark.net.hk) by pixar.com with SMTP id AA11538 (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Mon, 9 Oct 1995 23:02:43 -0700 Received: (from william@localhost) by is2.spark.net.hk (8.6.12/8.6.12) id NAA00693; Tue, 10 Oct 1995 13:37:42 +0800 Date: Tue, 10 Oct 1995 13:37:42 +0800 (HKT) From: william To: debian-bugs@pixar.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have found a problem when I terminate a telnet process from a debian linux server, then the process (bash) leaving in the server will going crazy and eat up all the cpu time. This only happen when I su to root. example: 1. telnet svr3 (my debian linux box) 2. after connect, su to root. 3. 'more' a file that will pause and ask u to continue. 4. press CTRL-] and quit to terminate the telnet session. 5. then there is a bash process running crazy in the svr3. I'm using bash-1.14.4-2. ----------------------------------------------------------------------- Message sent: From: iwj10@thor.cam.ac.uk (Ian Jackson) To: william Subject: Bug#1624: Acknowledgement (was: thermal run away problem) In-Reply-To: References: 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#1624" or "Re: Bug#1624" 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. Your message didn't have a Package: line at the start (in the pseudo-header following the real mail header), or didn't have a psuedo-header at all. This makes it much harder for us to categorise and deal with your problem report; please ensure that you say which package(s) and version(s) the problem is with next time. Some time in the future the problem reports system may start rejecting such messages. Ian Jackson (maintainer, debian-bugs) ----------------------------------------------------------------------- Message received at debian-bugs-request: From debian.org!imurdock Wed Oct 11 15:53:13 1995 Return-Path: Received: from pixar.com by mongo.pixar.com with smtp (Smail3.1.28.1 #15) id m0t3A1Q-000GoCC; Wed, 11 Oct 95 15:53 PDT Received: from imagine.imaginit.com by pixar.com with SMTP id AA11873 (5.67b/IDA-1.5 for debian-bugs-request-pipe@mongo.pixar.com); Wed, 11 Oct 1995 15:52:50 -0700 Received: by imagine.imaginit.com id (Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 11 Oct 95 17:57 EST Message-Id: Date: Wed, 11 Oct 95 17:57 EST From: imurdock@debian.org (Ian Murdock) To: debian-bugs-request@pixar.com reassign 1624 bash ----------------------------------------------------------------------- Ian Jackson / iwj10@thor.cam.ac.uk , with the debian-bugs tracking mechanism This page last modified 07:43:01 GMT Wed 01 Nov