Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!uport!admin!suprt!jmsully
From: jmsully@suprt.UUCP (John M. Sully)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: Another Annoying Microport Inquiry
Message-ID: <116@suprt.UUCP>
Date: Wed, 7-Oct-87 12:55:38 EDT
Article-I.D.: suprt.116
Posted: Wed Oct  7 12:55:38 1987
Date-Received: Sat, 10-Oct-87 08:52:02 EDT
References: <1408@dasys1.UUCP> <6475@brl-smoke.ARPA>
Organization: Microport Systems, Scotts Valley, CA
Lines: 21
Keywords: Microport patch ulimit
Summary: And the patch is...
Xref: mnetor comp.unix.wizards:4741 comp.unix.questions:4427

In article <6475@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
> In article <1408@dasys1.UUCP> manes@dasys1.UUCP (Steve Manes) writes:
> >What I'm looking for specifically is the patch address(es) for CDLIMIT,
> >which limits the maximum write address.  Currently, it's set at 2400 blocks
> >(1,228,800 bytes), which is way too small a filesize max for an application
> 
> ATTENTION ALL UNIX PORTERS:  Fix this!!  A 1Mb default ulimit is absolutely
> stupid!  Make the initial ulimit "infinite" (it can always be lowered by
> any user, typically in /etc/profile if the system administrator so chooses,
> but only a superuser can raise it).

The patch is:

patch /system5 ulpatch xxx

where xxx is the max filesize IN BLOCKS.  Currently this must be less than
32000, this problem has been fixed in 2.3.
-- 
John M. Sully         UUCP: ...!{sun | ucbvax | ihnp4}!amdcad!uport!techs
Microport Systems     ARPA: uport!techs@ucscc.UCSC.EDU
Technical Support