On Tue, 2006-01-24 at 10:08 +0100, Joerg Schilling wrote: > > the situation is messy; I can see some value in the hack Ted proposed to > > just bump the rlimit automatically at an mlockall-done-by-root.. but to > > be fair it's a hack :( > > As all other rlimits are honored even if you are root, it looks not orthogonal > to disregard an existing RLIMIT_MEMLOCK rlimit if you are root. that's another solution; give root a higher rlimit by default for this. It's also a bit messy, but a not-unreasonable default behavior. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Rationale for RLIMIT_MEMLOCK?
- From: "Theodore Ts'o" <tytso@mit.edu>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- References:
- Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Arjan van de Ven <arjan@infradead.org>
- Re: Rationale for RLIMIT_MEMLOCK?
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: GPL V3 and Linux
- Next by Date: Re: RCU latency regression in 2.6.16-rc1
- Previous by thread: Re: Rationale for RLIMIT_MEMLOCK?
- Next by thread: Re: Rationale for RLIMIT_MEMLOCK?
- Index(es):
![]() |