From nobody@FreeBSD.ORG Tue Aug 17 09:37:45 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 52188156D0; Tue, 17 Aug 1999 09:37:45 -0700 (PDT)
Message-Id: <19990817163745.52188156D0@hub.freebsd.org>
Date: Tue, 17 Aug 1999 09:37:45 -0700 (PDT)
From: slawson@alphamicro.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: Easy for user to crash system
X-Send-Pr-Version: www-1.0

>Number:         13202
>Category:       misc
>Synopsis:       Easy for user to crash system
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 17 09:40:00 PDT 1999
>Closed-Date:    Tue Sep 21 16:33:45 PDT 1999
>Last-Modified:  Tue Sep 21 16:40:00 PDT 1999
>Originator:     Steven Lawson
>Release:        2.2.8
>Organization:
Alpha Microsystems
>Environment:
>Description:
In an attempt to lure one of our hardware guys from Linux to FreeBSD,
we installed 2.2.8 on a system.  A "make it do something" test he
runs on Linux, and on the SCO Openserver boxes on the production
floor, killed FreeBSD very quickly.  It was quite embarrasing, being
so simple.  It's just a looping batch file which appears to rapidly
eat all of swap, while he insists the other boxes handle it fine.
>How-To-Repeat:
Create a file called "looptest", which contains:
   ls -l
   ./looptest

Make it executable and run it.  System performance drops
and before long it's griping about lack of swap and attempts
to log into the other virtual consoles fail.
>Fix:


>Release-Note:
>Audit-Trail:

From: The Tech-Admin Dude <geniusj@phoenix.unacom.com>
To: slawson@alphamicro.com
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: misc/13202: Easy for user to crash system
Date: Tue, 17 Aug 1999 21:17:15 -0400 (EDT)

 I recommend using login accounting, that is what it is there for :)..
 /etc/login.conf.. How much swap was there? What was MAXUSERS set to?
 normally, for an ls, if you have maxusers at default, i'm surprised you
 didnt run out of processes before it crashed, must have low swap? Anyway,
 main point, USE LOGIN ACCOUNTING :)
 
 
 
 ------------------------------------------------------------------------------
 Jason DiCioccio                              | geniusj@free-bsd.org
 FreeBSD - The Power to Serve                 | http://www.freebsd.org
 Tel: (303) 984-5311                          | http://www.nailed.com
 ------------------------------------------------------------------------------
 
 On Tue, 17 Aug 1999 slawson@alphamicro.com wrote:
 
 > 
 > >Number:         13202
 > >Category:       misc
 > >Synopsis:       Easy for user to crash system
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Tue Aug 17 09:40:00 PDT 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Steven Lawson
 > >Release:        2.2.8
 > >Organization:
 > Alpha Microsystems
 > >Environment:
 > >Description:
 > In an attempt to lure one of our hardware guys from Linux to FreeBSD,
 > we installed 2.2.8 on a system.  A "make it do something" test he
 > runs on Linux, and on the SCO Openserver boxes on the production
 > floor, killed FreeBSD very quickly.  It was quite embarrasing, being
 > so simple.  It's just a looping batch file which appears to rapidly
 > eat all of swap, while he insists the other boxes handle it fine.
 > >How-To-Repeat:
 > Create a file called "looptest", which contains:
 >    ls -l
 >    ./looptest
 > 
 > Make it executable and run it.  System performance drops
 > and before long it's griping about lack of swap and attempts
 > to log into the other virtual consoles fail.
 > >Fix:
 > 
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > 
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 > 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Tue Sep 21 16:33:45 PDT 1999 
State-Changed-Why:  
Not a bug. 

From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
To: slawson@alphamicro.com
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/13202: Easy for user to crash system
Date: 22 Sep 1999 01:36:42 +0200

 slawson@alphamicro.com writes:
 > Create a file called "looptest", which contains:
 >    ls -l
 >    ./looptest
 
 This is a fork bomb (linear, not quadratic, but still a fork bomb).
 Use resource limits to prevent it from eating up all system resources
 (see login.conf(5)). And please use a more recent version than 2.2.8.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@flood.ping.uio.no
 
>Unformatted:
