14 Sep
2005
14 Sep
'05
4:01 p.m.
On Mon, Sep 12, 2005 at 03:06:09PM -0400, Lee Revell wrote:
I see. At the moment it seems to be a useable workaround. But, it's good
to know that it is not a permament solution.
--
Eric Dantan Rzewnicki | Systems Administrator
Technical Operations Division | Radio Free Asia
2025 M Street, NW | Washington, DC 20036 | 202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any
unauthorized dissemination, distribution, or copying is strictly
prohibited. If you receive this transmission in error, please contact
network(a)rfa.org.
On Mon, 2005-09-12 at 14:51 -0400, Eric Dantan
Rzewnicki wrote:
ok. I'll try to find some time to look at the glibc list archive.
On Sun, Sep 11, 2005 at 03:00:53PM -0400, Lee
Revell wrote:
Check the glibc development mailing list for
details. The new rlimits
are supported in their development branch IIRC. On Sun, 2005-09-11 at 16:10 +0200, Michael Rudolf
wrote:
I thought it was just
pam that needed changing to use the rt rlimits.
What needs to be done in glibc? 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 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.