On Fri, 04 Jul 2003 13:58:02 +1000
matthew green <mrg@eterna.com.au> wrote:

> this is a common problem with "proc.curproc".  when you run
> sysctl, it changes only change's itself - it's the current
> "curproc" after all.  you have to run it like:
> 
> 	#! /bin/sh
> 
> 	sysctl -w proc.$$.rlimit.datasize.hard=bignumberhere

	I had tried this earlier as directed by csh(1), but to no avail. That
command sets the resource limits for the current shell and should be
reflected in inherited limits by a subsequent sysctl to check the
current value (which would be reflective of the parent process) no?

-Steve