Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!rutgers!columbia!cunixc!sethr
From: sethr@cunixc.cc.columbia.edu (Seth Robertson)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit (was: getty/login for callback)
Message-ID: <1423@cunixc.cc.columbia.edu>
Date: 18 Apr 89 17:18:21 GMT
References: <180001@mechp10.UUCP> <13853@rpp386.Dallas.TX.US> <797@twwells.uucp> <28@wells.UUCP> <399@aucis.UUCP> <501@bilver.UUCP> <19516@genrad.UUCP> <10065@smoke.BRL.MIL>
Reply-To: seth@ctr.columbia.edu (Seth Robertson)
Organization: Columbia University:  Center for Telecommunications Research
Lines: 15

In article <10065@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
|In article <19516@genrad.UUCP> jpn@genrad.genrad.COM (John P. Nelson) writes:
||Despite the tone, I really would be happy if someone could demonstrate
||a useful purpose for "ulimit".
|
|It's great for testing whether your application recovers gracefully from
|"file system full"-like conditions!

There's a *much* better way to determine in your application recovers
gracefully from "file system full"-like conditions, and thats to fill
up your file system.  I don't know about you, but I've never had *any*
problem testing that condition (whether I wanted to or not!)

					-Seth
					 seth@ctr.columbia.edu