Re: [cgiwrap-users] rlimit nproc

[Tuc <tu...@tt...>]

> 
> Well, you ran "./configure"... it did exactly what it's supposed to. None 
> of those rlimit limit are turned on unless you specfifically request them 
> to be turned on.
> 
> You need to specify --with-rlimit-nproc or --with-rlimit-nproc=XX
>
	Understandable... The issue is if you DON'T specify, then its almost
like saying --with-rlimit-nproc=999999999 . 8-)  
> 
> As far as what it does, it simply issues the setrlimit() system call prior 
> to executing your script. It's a standard O/S facility. See setrlimit man 
> page on your O/S. 
>
	DISCLAIMER: I'm not a C/C++ programmer.

	My man page says :


     Limits on the consumption of system resources by the a process and each
     process it creates may be obtained with the getrlimit() or getprlimit()
     call, and set with the setrlimit() or setprlimit() call.


	My take would be that the CGIWRAP process is something that starts,
runs the underling, and stops. Wouldn't it be useless for 100 CGIWRAPS to 
set it to 32?

     RLIMIT_NPROC    The maximum number of simultaneous processes for this us-
                     er id.


	and later on 

     Because this information is stored in the per-process information, this
     system call must be executed directly by the shell if it is to affect all
     future processes created by the shell.  Most shells have a limit, ulimit
     or unlimit built-in command.

	Or is it just that NPROC applies to ANY running process? And what
if someone else set it to 100?

	Are you setting the hard/soft to be the same?


		Thanks, Tuc/TTSG Internet Services, Inc.