From owner-freebsd-bugs  Wed May  6 02:09:34 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA16607
          for freebsd-bugs-outgoing; Wed, 6 May 1998 02:09:34 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16538;
          Wed, 6 May 1998 02:09:09 -0700 (PDT)
          (envelope-from phk@FreeBSD.org)
From: Poul-Henning Kamp <phk@FreeBSD.ORG>
Received: (from phk@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id CAA10019;
	Wed, 6 May 1998 02:06:25 -0700 (PDT)
Date: Wed, 6 May 1998 02:06:25 -0700 (PDT)
Message-Id: <199805060906.CAA10019@freefall.freebsd.org>
To: chern@tiger.towson.edu, phk@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: bin/2925
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: non-priviledged user can crash FreeBSD!!

State-Changed-From-To: open-closed
State-Changed-By: phk
State-Changed-When: Wed May 6 02:05:43 PDT 1998
State-Changed-Why: 
Analyzed by koshy@india.hp.com:
post addition of login class functionality
a sysadmin can restrict the usage of system resources by a process.
Hence non-priviledged users can be prevented from crashing FreeBSD.

(The deeper of problem of recovering from an arbitrary OS resource 
 running out is not easy to fix.  But at least we have now knobs to 
 which allow us to tackle the easier cases).

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message