Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261464AbVAGPmZ (ORCPT ); Fri, 7 Jan 2005 10:42:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261467AbVAGPmZ (ORCPT ); Fri, 7 Jan 2005 10:42:25 -0500 Received: from out009pub.verizon.net ([206.46.170.131]:41423 "EHLO out009.verizon.net") by vger.kernel.org with ESMTP id S261464AbVAGPlm (ORCPT ); Fri, 7 Jan 2005 10:41:42 -0500 Message-Id: <200501071541.j07FfeQC018553@localhost.localdomain> To: Arjan van de Ven cc: Christoph Hellwig , Lee Revell , Ingo Molnar , Chris Wright , Alan Cox , "Jack O'Quin" , Linux Kernel Mailing List , Andrew Morton Subject: Re: [PATCH] [request for inclusion] Realtime LSM In-reply-to: Your message of "Fri, 07 Jan 2005 16:33:30 +0100." <20050107153328.GD28466@devserv.devel.redhat.com> Date: Fri, 07 Jan 2005 10:41:40 -0500 From: Paul Davis X-Authentication-Info: Submitted using SMTP AUTH at out009.verizon.net from [151.197.185.179] at Fri, 7 Jan 2005 09:41:41 -0600 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 803 Lines: 23 >> well thats good, i hope someone updated the man page too :) >> >> but is there actually any way to grant specific users a reasonable >> rlimit, > >yes; most distributions will use pam for this, you can set per user or per >gorup limits there. isn't that a uid/gid based system? ok, i'm being a little snide :) fine, so the mlock situation may have improved enough post-2.6.9 that it can be considered fixed. that leaves the scheduler issue. but apparently, a uid/gid solution is OK for mlock, and not for the scheduler. am i missing something? --p - 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/