mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-09-02 07:15:27 +00:00
Code Issues Releases Wiki Activity

The new parser doesn't have the old ordering constraints.

Browse Source
This commit is contained in:
Todd C. Miller
2004-10-26 20:08:47 +00:00
parent 92d0954bcc
commit b7479ce1e2
1 changed files with 3 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
sudoers.pod
View File

@@ -32,8 +32,8 @@ The I<sudoers> file is composed of two types of entries: aliases
may run what). may run what).
When multiple entries match for a user, they are applied in order. When multiple entries match for a user, they are applied in order.
Where there are conflicting values, the last match is used (which Where there are multiple matches, the last match is used (which is
is not necessarily the most specific match). not necessarily the most specific match).
The I<sudoers> grammar will be described below in Extended Backus-Naur The I<sudoers> grammar will be described below in Extended Backus-Naur
Form (EBNF). Don't despair if you don't know what EBNF is; it is Form (EBNF). Don't despair if you don't know what EBNF is; it is
@@ -243,10 +243,7 @@ by default.
If set, B<sudo> will ignore '.' or '' (current dir) in the C<PATH> If set, B<sudo> will ignore '.' or '' (current dir) in the C<PATH>
environment variable; the C<PATH> itself is not modified. This environment variable; the C<PATH> itself is not modified. This
flag is I<@ignore_dot@> by default. Currently, while it is possible flag is I<@ignore_dot@> by default.
to set I<ignore_dot> in I<sudoers>, its value is not used. This option
should be considered read-only (it will be fixed in a future version
of B<sudo>).
=item mail_always =item mail_always
@@ -1015,13 +1012,6 @@ used as part of a word (e.g. a username or hostname):
=head1 EXAMPLES =head1 EXAMPLES
Since the I<sudoers> file is parsed in a single pass, order is
important. In general, you should structure I<sudoers> such that
the C<Host_Alias>, C<User_Alias>, and C<Cmnd_Alias> specifications
come first, followed by any C<Default_Entry> lines, and finally the
C<Runas_Alias> and user specifications. The basic rule of thumb
is you cannot reference an Alias that has not already been defined.
Below are example I<sudoers> entries. Admittedly, some of Below are example I<sudoers> entries. Admittedly, some of
these are a bit contrived. First, we define our I<aliases>: these are a bit contrived. First, we define our I<aliases>: