On Mon, 2005-09-12 at 14:51 -0400, Eric Dantan Rzewnicki wrote:
On Sun, Sep 11, 2005 at 03:00:53PM -0400, Lee Revell
wrote:
On Sun, 2005-09-11 at 16:10 +0200, Michael Rudolf
wrote:
Lee Revell wrote:
Yes, that is almost certainly the problem.
The /tmp entry in /etc/fstab should look like this:
tmpfs /tmp tmpfs defaults 0
0
Unfortunately, that didn't seem to help - I get the same symptoms as before
(attached below).
I'm heading for a 2.6.13 kernel with realtime-preempt patch now. I'm afraid
this is going to get complicated because of rtlimits/PAM setup.
Just use the
realtime LSM. The rtlimits/PAM stuff is not ready yet
(glibc needs to catch up, until then it's just a hack).
I thought it was just pam that needed changing to use the rt rlimits.
What needs to be done in glibc?
Check the glibc development mailing list for details. The new rlimits
are supported in their development branch IIRC.
I have patched pam packages for debian sarge on
techweb.rfa.org/debrfa/
which seem to be working fine for me with 2.6.13.
PAM is supposed to get the list of rlimits from glibc. Patching PAM
directly is just a hack/workaround.
Lee