Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ukma!rutgers!bellcore!texbell!bigtex!pmafire!dave
From: dave@pmafire.UUCP (Dave Remien)
Newsgroups: comp.bugs.sys5
Subject: Re: ulimit -- You don't need sources!
Keywords: ULIMIT in kernel?
Message-ID: <635@pmafire.UUCP>
Date: 14 May 89 05:33:10 GMT
References: <836@twwells.uucp> <4428@ihuxz.ATT.COM> <545@aurora.AthabascaU.CA> <697@occrsh.ATT.COM> <476@loft386.UUCP>
Reply-To: dave@pmafire.UUCP (Dave Remien)
Organization: WINCO, INEL, Idaho
Lines: 22

In article <476@loft386.UUCP> dpi@loft386.UUCP (Douglas P. Ingraham) writes:
>
>Page 43 of the SYS V 386 Release 3.2 RELEASE NOTES is quite clear on how
>to change ULIMIT for logins.  I suspect versions for other systems also
>allow ULIMIT to be changed in the file /etc/default/login.

This discussion about the various ways of changing ULIMT has been
interesting, but no one has asked what I think is the most interesting
question - why on earth is there a 12288 block limit in
/etc/conf/cf.d/mtune anyway? Suppose I want to create a file greater
than 6 megs? Why should the kernel care? Heck, the source for X11R3,
tar'ed and compressed is 8 megs long, and even root can't bring it over
and do anything with it. 

Is there some silly limit in the kernel, or can we change mtune and do
some real work? I guess I'll try on Monday, and find out. (Can't reboot
it from home ;-). 

-- 
Dave Remien - WINCO Computer Eng. Group -{uunet | bigtex}!pmafire!dave- 
"I'm looking for the same old place.  You must mean the old same place. 
It's right out back, sonny, here's the key." (Firesign Theater, ca. 1970)