Path: utzoo!mnetor!tmsoft!dptcdc!berner!lethe!geac!jtsv16!uunet!lll-winken!ames!rex!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit (was: getty/login for callback)
Message-ID: <829@twwells.uucp>
Date: 19 Apr 89 05:08:23 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> <1423@cunixc.cc.columbia.edu>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 24
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <1423@cunixc.cc.columbia.edu> seth@ctr.columbia.edu (Seth Robertson) writes:
: In article <10065@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
: |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.

If I decided to fill up any file system on my work machines, I'd be
fired the second time I tried it.

If I filled up either partition on my home machine, it would very
likely break something.

I suspect that there are very few environments where it is reasonable
to fill up file systems just because you want to test out "file
system full" checking.

---
Bill                            { uunet | novavax } !twwells!bill
(BTW, I'm may be looking for a new job sometime in the next few
months.  If you know of a good one where I can be based in South
Florida do send me e-mail.)