This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Fri Mar 29 01:43:00 2024 Received: from nic.funet.fi (nic.funet.fi [128.214.248.6]) by herbie.ucs.indiana.edu (8.7.5/8.6.12) with ESMTP id OAA00211 for ; Thu, 20 Mar 1997 14:23:03 -0500 (EST) Received: from vger.rutgers.edu ([128.6.190.2]) by nic.funet.fi with ESMTP id <3431-28165>; Thu, 20 Mar 1997 21:00:57 +0200 Received: by vger.rutgers.edu id <213228-492>; Thu, 20 Mar 1997 13:40:48 -0500 From: David Wong Message-Id: <199703201834.AA08420@magnum.cooper.edu> Subject: Re: Star Trek Window Manager To: mdean@best.com (mdean) Date: Thu, 20 Mar 1997 13:34:08 -0500 (EST) Cc: linux-kernel@vger.rutgers.edu, unlisted-recipients:; In-Reply-To: from "mdean" at Mar 19, 97 11:42:51 pm X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk does anyone have patches that would set limits on the number of processes a user can have. > > > > Both hit the process limit pretty quickly, but the shell script > > version kills the machine pretty much dead. > > > > No-one else can log in, Control-c doesn't work, and when I try > > Ctrl-Alt-Delete, the system takes about five minutes to get to > > "Shutting down gpm services: ", and does nothing after that. > > (Well, I waited 15 minutes, and gave up and hit the reset button.) > > > > It seems to me that this may be something to do with the fact that > > the processes are respawning faster than init can kill them. > > > > Perhaps init should be modified to send the a SIGSTOP before > > SIGTERM/SIGKILL. This would (might?) solve this problem. > > > > Matthew. > > > > -- > > Matthew Kirkwood | Mail: weejock@ferret.lmh.ox.ac.uk > > LMH JCR, | Web: http://www-jcr.lmh.ox.ac.uk/~weejock/ > > Oxford OX2 6QA, | Microsoft: "Where do you want to go today?" > > England. | Linux: "Where you want to go _now_?" > > > > > > -- David Wong