From owner-p4-projects@FreeBSD.ORG Sun Oct 11 17:29:28 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 87D641065676; Sun, 11 Oct 2009 17:29:28 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C6AB1065672 for ; Sun, 11 Oct 2009 17:29:28 +0000 (UTC) (envelope-from trasz@freebsd.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 197FB8FC20 for ; Sun, 11 Oct 2009 17:29:28 +0000 (UTC) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n9BHTRkU061011 for ; Sun, 11 Oct 2009 17:29:27 GMT (envelope-from trasz@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n9BHTRdY061009 for perforce@freebsd.org; Sun, 11 Oct 2009 17:29:27 GMT (envelope-from trasz@freebsd.org) Date: Sun, 11 Oct 2009 17:29:27 GMT Message-Id: <200910111729.n9BHTRdY061009@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to trasz@freebsd.org using -f From: Edward Tomasz Napierala To: Perforce Change Reviews Cc: Subject: PERFORCE change 169409 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2009 17:29:28 -0000 http://perforce.freebsd.org/chv.cgi?CH=169409 Change 169409 by trasz@trasz_victim on 2009/10/11 17:28:33 Fix language errors. Affected files ... .. //depot/projects/soc2009/trasz_limits/usr.sbin/hrl/hrl.8#2 edit Differences ... ==== //depot/projects/soc2009/trasz_limits/usr.sbin/hrl/hrl.8#2 (text+ko) ==== @@ -76,10 +76,10 @@ Syntax for a rule is subject:subject-id:resource:action=amount/per. .Pp Subject defines the kind of entity the rule applies to. -It can be either process, user, group, loginclass, or jail. +It can be either process, user, group, login class, or jail. .Pp Subject ID identifies the subject. It can be user name, group name, -loginclass name, or a numerical UID, GID, or JID. +login class name, or a numerical UID, GID, or JID. .Pp Resource identifies the resource the rule controls. .Pp @@ -92,19 +92,21 @@ .Pp The per field defines what entity the limit gets accounted for. For example, rule "loginclass:users:memoryuse:deny=100M/process" means -that each process of a user belonging to loginclass "users" may use up to 100MB +that each process of any user belonging to login class "users" may use up to 100MB of memory. Rule "loginclass:users:memoryuse:deny=100M/user" would mean that the sum of -memory used by all processes of that user will not exceed 100MB. +memory used by all processes of any user belonging to the login class "users" +will not exceed 100MB. Rule "loginclass:users:memoryuse:deny=100M/loginclass" would mean that the sum of -memory used by all processes of all users with that loginclass will not exceed 100MB. +memory used by all processes of all users belonging to that login class will +not exceed 100MB. .Pp Valid rule has all of these fields specified, except for the per, which defaults to the value of subject. .Pp A filter is a rule for which one of more fields other than per is left empty. For example, a filter that matches every rule could be written as ":::=/", -or, in short, ":". A filter that matchess all the login classes would be +or, in short, ":". A filter that matches all the login classes would be "loginclass:". A filter that matches all defined limits for maxprocesses resource would be "::maxprocesses". .Sh EXIT STATUS