lkml.org 
[lkml]   [2006]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: Rationale for RLIMIT_MEMLOCK?
    From
    Date
    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/

    \
     
     \ /
      Last update: 2006-01-24 10:18    [W:2.668 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site