Path: utzoo!attcan!uunet!wuarchive!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!csd4.csd.uwm.edu!uakari.primate.wisc.edu!indri!ames!sun-barr!rutgers!bellcore!texbell!nuchat!moray!splut!jay
From: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Newsgroups: comp.unix.microport
Subject: Re: Ulimit on Sys V/AT?
Message-ID: <2840@splut.conmicro.com>
Date: 24 Aug 89 11:31:49 GMT
References: <267@opel.UUCP>
Reply-To: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Organization: Confederate Microsystems, League City, TX
Lines: 28

In article <267@opel.UUCP> johnk@opel.UUCP (John Kennedy) writes:
>I'm sure this has been worked into the ground, but is there
>not a kernel location that can be patched on Sys V/AT 2.4
>that increases the ulimit across the board?

Yup. It's called ulpatch. By default, it's 1228800 bytes (2400 512-byte
blocks):
Script started Thu Aug 24 06:25:08 1989
(114) root@splut:/: patch /unix.2.4.0 ulpatch
0x960

You can increase  it (or decrease it, though I have no idea why you'd
want to) by using /etc/patch to change this value, as I've done to my
system:
(115) root@splut:/: patch /system5 ulpatch
0x7fff
This runs it up to 16 MB - which oughtta be enough. (I don't know if
this is a signed number or not, or if it's a short or a long - anyone
out there know more?) Just say,
patch /system5 ulpatch 0x7fff
and reboot. If you wanna save yourself the boot, just reissue the same
command, adding the -k switch to patch kernel memory.

-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL   | Never ascribe to malice that which can
jay@splut.conmicro.com       (eieio)| adequately be explained by stupidity.
{attctc,bellcore}!texbell!splut!jay +----------------------------------------
"Rabid rerouters *love* to route mail to devnull@hell.org" - Brandon Allbery