Article View: comp.bugs.sys5
Article #1049Re: ulimit (was: getty/login for callback)
From: SuperUser
Date: Sat, 22 Apr 1989 00:07
Date: Sat, 22 Apr 1989 00:07
19 lines
1466 bytes
1466 bytes
In article <829@twwells.uucp>, bill@twwells.uucp (T. William Wells) writes: > 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! > > [no, fill a file system] > 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. However, using ulimit() to test that makes it harder to discover that your application recovers from that by creating another file and logging a message to it. If you aren't going to buy enough hardware to properly test your software, why bother with testing at all? -- John Woods, Charles River Data Systems, Framingham MA, (508) 626-1101 ...!decvax!frog!john, john@frog.UUCP, ...!mit-eddie!jfw, jfw@eddie.mit.edu
Technical Details
Message-ID:
<1295@frog.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!seismo!sundc!pitstop!texsun!texbell!bellcore!clyde!ima!mirror!frog!johnReferences:
<180001@mechp10.UUCP> <13853@rpp386.Dallas.TX.US> <797@twwells.uucp> <829@twwells.uucp>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!seismo!sundc!pitstop!texsun!texbell!bellcore!clyde!ima!mirror!frog!john From: john@frog.UUCP (SuperUser) Newsgroups: comp.bugs.sys5 Subject: Re: ulimit (was: getty/login for callback) Message-ID: <1295@frog.UUCP> Date: 22 Apr 89 00:07:00 GMT References: <180001@mechp10.UUCP> <13853@rpp386.Dallas.TX.US> <797@twwells.uucp> <829@twwells.uucp> Organization: Misanthropes-R-Us Lines: 19