On 07/25/12 19:06, Chet Ramey wrote:
Well, _SC_CHILD_MAX is documented across platforms as:
Heck, even POSIX specifies CHILD_MAX as:
"Maximum number of simultaneous processes per real user ID."
Also, one Linux machine actually shows the _SC_CHILD_MAX value equal to
kernel.pid_max (32768 here
Hi all,
I'm not sure whether I should post this here. Sorry if disturb.
We met a very strange problem with bash "version 3.00.15(1)-release". We are
using a hadoop-test script to test whether a file exists on HDFS. But we
observed several times that the hadoop-test script, which is a subscript
On Thu, Jul 26, 2012 at 02:48:30AM -0700, wangzhong@gmail.com wrote:
> Hi all,
>
> I'm not sure whether I should post this here. Sorry if disturb.
help-bash would be a better choice than bug-bash.
> We met a very strange problem with bash "version 3.00.15(1)-release". We are
> using a hadoop
On 7/25/12 1:08 PM, Chet Ramey wrote:
> On 7/25/12 11:33 AM, Andreas Schwab wrote:
>
>> I cannot see how CHILD_MAX is related to pid reuse. CHILD_MAX is a
>> per-user limit, but the pid namespace is global. If the shell forks a
>> new process, and the pid of it matches one of the previously used
On 07/26/12 20:29, Chet Ramey wrote:
OK, we have some data, we have a hypothesis, and we have a way to test it.
Let's test it.
Michael, please apply the attached patch, disable RECYCLES_PIDS, and run
your tests again. This makes the check for previously-saved exit statuses
unconditional.
Let'
