Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Aug 1999 10:30:02 -0700 (PDT)
From:      The Tech-Admin Dude <geniusj@phoenix.unacom.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/13202: Easy for user to crash system
Message-ID:  <199908171730.KAA53434@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/13202; it has been noted by GNATS.

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
 > 
 
 


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908171730.KAA53434>