Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!forys
From: forys@sigi.Colorado.EDU (Jeff Forys)
Newsgroups: comp.unix.wizards
Subject: Re: Memoryuse limit
Message-ID: <2624@sigi.Colorado.EDU>
Date: Sun, 18-Oct-87 07:37:29 EDT
Article-I.D.: sigi.2624
Posted: Sun Oct 18 07:37:29 1987
Date-Received: Sun, 18-Oct-87 23:43:07 EDT
References: <2369@umn-cs.UUCP>
Reply-To: forys@boulder.Colorado.EDU (Jeff Forys)
Organization: University of Colorado, Boulder
Lines: 24
Keywords: memory limit

In article <2369@umn-cs.UUCP> murray@umn-cs.UUCP (William Murray) writes:
> We have a Vax 11/780 running Mt. Xinu.  At some point during the run, the
> system gives [a] message such as "memoryuse limit reached" and then stops
> execution of the program.

Your kernel is complaining about your memoryuse limit?  Is this an added
feature from Mt. Xinu?  As far as I know, under 4.3BSD, nothing actually
checks your memoryuse limit, however, next time the pageout daemon gets
fired up, your process becomes a prime candidate for having it's pages
stealed.  Did I overlook something in there (hard to believe :-)?

> I have looked for a way to increase the memoryuse for the user but so
> far haven't found the answer.

The resource limits (including memoryuse) can be raised/lowered using
the "limit" command of `csh'.  It is documented in the `csh' manual
page.  Under 4.2/3 BSD, the limit defaults to nearly all of available
memory.  If the command `limit memoryuse' yields "umlimited" (4.2BSD)
or equals `limit -h memoryuse' (4.3BSD) the limit can not be raised
without "superuser intervention" (i.e. you'll have to write a little
setuid-root program for him).
---
Jeff Forys @ UC/Boulder Engineering Research Comp Cntr (303-492-4991)
forys@boulder.Colorado.EDU  -or-  ..!{hao|nbires}!boulder!forys