Yesterday I installed 2.2.19 one of out alpha servers and I found that it
still has the same bug that we patched 2.2.14 to get rid of. In the 2.4 line
it seems to be fixed.
The bug has the affect that a unprev. user cannot increase the stack limit
even if he/she is allowed to.
This mailing list item fom Jun 12 2000 describes the problem:
<snippit from page>
It is because wrong value in the
The INIT_RLIMITS defined the RLIMIT_STACK as
The latter defines hard limit of the stack.
When I pointed the problem, only Intel and PPC people corrected it.
You should change the value as
and recompile your kernel.
It will resolve your problem.
</snippit from page>
I can report that is does resolve the problem here. Is this a bug or is the
kernel supposed to work that way?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:15 EST