Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ucsd!rutgers!mcdchg!falkor!heiby
From: heiby@falkor.UUCP (Ron Heiby)
Newsgroups: news.software.b
Subject: Re: news software speedup
Message-ID: <159@falkor.UUCP>
Date: 30 Mar 88 14:16:58 GMT
References: <649@bms-at.UUCP> <10150@ncc.UUCP> <4246@hoptoad.uucp> <10128@steinmetz.steinmetz.ge.com> <4265@hoptoad.uucp>
Reply-To: heiby@mcdchg.UUCP (Ron Heiby)
Organization: Luck Dragons, Magic, & Friends
Lines: 20

John Gilmore (gnu@hoptoad.uucp) writes:
> davidsen@steinmetz.steinmetz.ge.com (William E. Davidsen Jr) wrote:
> >                                Obviously having the ulimit (or any other
> > configurable parameter) set to an inappropriate value is a "vendor
> > problem" rather than a "System V bug."
> 
> If it's a "vendor problem" howcum all the Sys V vendors have the problem?

Proof by counter-example:  Motorola Microcomputer Division's VME Delta
Series computers use System V Release 3.0 and have "ulimit" as a tunable
parameter.  So, you see, at least one vendor has "fixed" this "bug".

(A bit of history:  When AT&T entered the computer business (commercially),
some of us (I used to work there.) saw the 1Meg ulimit as a bad thing.  Over
the course of about two years, we managed to get UNIX development to make
it a tunable.  It is tunable in AT&T's Release 3.1.  The value is referenced
a total of ONE place in the kernel.)
-- 
Ron Heiby, heiby@mcdchg.UUCP	Moderator: comp.newprod & comp.unix
"I believe in the Tooth Fairy."  "I believe in Santa Claus."
	"I believe in the future of the Space Program."