On Fri, Jul 8, 2011 at 9:18 AM, Cal Leeming [Simplicity Media Ltd] <[email protected]> wrote: > In the above scenario, ulimit would apply that limit to everything > within that forked supervisord instance, correct? > > Therefore, if nginx-wrapper calls ulimit at almost the exact same > point as other-wrapper, there could be a race condition between the > time it takes to jump from ulimit to the binary, where the wrong > address space is inherited.
if nginx-wrapper and other-wrapper is each one a different process, then ulimit would affect only to that process and descendants. it doesn't propagate to brother-processes besides, this is posix we're talking about; there are no race conditions in calling executables or atomic system calls -- Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
