Xref: utzoo unix-pc.general:3732 comp.sys.att:7584
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!aplcen!haven!umbc3!mark
From: mark@umbc3.UMBC.EDU (Mark Sienkiewicz)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: u.u_limit structure on UNIXPC
Keywords: Process limits
Message-ID: <2309@umbc3.UMBC.EDU>
Date: 16 Sep 89 02:54:22 GMT
References: <2725@umn-d-ub.D.UMN.EDU>
Reply-To: mark@umbc3.umbc.edu.UMBC.EDU (Mark Sienkiewicz)
Distribution: na
Organization: University of Maryland, Baltimore County
Lines: 18

In article <2725@umn-d-ub.D.UMN.EDU> rhealey@ub.d.umn.edu (Rob Healey) writes:
>
>	How does one set/modify the limits in the u.u_limit array for
>	the user under 3.5x? See /usr/include/sys/vlimit.h for details.

In fact, there is no stock way to set the interesting limits.  If you
write some new kernel code, you can change the values, but this has
no effect on anything.

There are 3 (?) limits that you can set using the SYSV ulimit() call
documented in your manual.  Apparently CT had to break the OS in several
places to make it SVID compliant. :(

-- 
			Mark S.

uunet!umbc3!nerwin!zilla!mark
nerwin!zilla!mark@umbc3.umbc.edu