From: Todd C. Miller Date: Tue, 26 Oct 2004 20:08:47 +0000 (+0000) Subject: The new parser doesn't have the old ordering constraints. X-Git-Tag: SUDO_1_7_0~874 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b7479ce1e221906702955467dea211b03243ca69;p=sudo The new parser doesn't have the old ordering constraints. --- diff --git a/sudoers.pod b/sudoers.pod index 3698ce5f2..65a8e9f50 100644 --- a/sudoers.pod +++ b/sudoers.pod @@ -32,8 +32,8 @@ The I file is composed of two types of entries: aliases may run what). When multiple entries match for a user, they are applied in order. -Where there are conflicting values, the last match is used (which -is not necessarily the most specific match). +Where there are multiple matches, the last match is used (which is +not necessarily the most specific match). The I grammar will be described below in Extended Backus-Naur Form (EBNF). Don't despair if you don't know what EBNF is; it is @@ -243,10 +243,7 @@ by default. If set, B will ignore '.' or '' (current dir) in the C environment variable; the C itself is not modified. This -flag is I<@ignore_dot@> by default. Currently, while it is possible -to set I in I, its value is not used. This option -should be considered read-only (it will be fixed in a future version -of B). +flag is I<@ignore_dot@> by default. =item mail_always @@ -1015,13 +1012,6 @@ used as part of a word (e.g. a username or hostname): =head1 EXAMPLES -Since the I file is parsed in a single pass, order is -important. In general, you should structure I such that -the C, C, and C specifications -come first, followed by any C lines, and finally the -C and user specifications. The basic rule of thumb -is you cannot reference an Alias that has not already been defined. - Below are example I entries. Admittedly, some of these are a bit contrived. First, we define our I: