ody has found a solution yet. I hope that someone with
the knowledge to do so will take this seriously in the near future, as
it seems to affect more and more people.
Thanks for your answer. It seems that forcing the affinity of the
first bash process to only one CPU solves this issue.
--
esult file always contains 0 (shouldn't it be
non-null, as the last process creation failed ?)
I don't know where to look to find more information about this
problem. Has anyone already seen it, or is there something else I
could do to find out more ?
(outputs of ulimit -a and cygcheck -s -
2 matches
Mail list logo
