rhealey@ub.d.umn.edu (Rob Healey) (09/12/89)
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. IS there any way you can set these so your core files, CPU time, etc is actually limited? I didn't see the SIGNALS involved in the limits defined anywhere. Just VERY curious if this is just another dead end brought to you by Convergent and the mortal remains of CTIX within the UNIX PC. -Rob Healey rhealey@ub.d.umn.edu
mark@umbc3.UMBC.EDU (Mark Sienkiewicz) (09/16/89)
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
comeau@utoday.UUCP (Greg Comeau) (09/20/89)
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. I check about that many moons ago and came across a dead end. Seems that these fields are basically bogus in this implemntation.