"upper case" -> "uppercase"
This commit is contained in:
@@ -109,9 +109,9 @@ Each I<alias> definition is of the form
|
||||
Alias_Type NAME = item1, item2, ...
|
||||
|
||||
where I<Alias_Type> is one of C<User_Alias>, C<Runas_Alias>, C<Host_Alias>,
|
||||
or C<Cmnd_Alias>. A C<NAME> is a string of upper case letters, numbers,
|
||||
or C<Cmnd_Alias>. A C<NAME> is a string of uppercase letters, numbers,
|
||||
and the underscore characters ('_'). A C<NAME> B<must> start with an
|
||||
upper case letter. It is possible to put several alias definitions
|
||||
uppercase letter. It is possible to put several alias definitions
|
||||
of the same type on a single line, joined by a colon (':'). E.g.,
|
||||
|
||||
Alias_Type NAME = item1, item2, item3 : NAME = item4, item5
|
||||
|
@@ -88,7 +88,7 @@ B<visudo> accepts the following command line options:
|
||||
Enable B<strict> checking of the I<sudoers> file. If an alias is
|
||||
used before it is defined, B<visudo> will consider this a parse
|
||||
error. Note that it is not possible to differentiate between an
|
||||
alias and a hostname or username that consists solely of upper case
|
||||
alias and a hostname or username that consists solely of uppercase
|
||||
letters, digits, and the underscore ('_') character.
|
||||
|
||||
=item -V
|
||||
@@ -118,7 +118,7 @@ Your userid does not appear in the system passwd file.
|
||||
|
||||
Either you are using a {User,Runas,Host,Cmnd}_Alias before
|
||||
defining it or you have a user or hostname listed that
|
||||
consists solely of upper case letters, digits, and the
|
||||
consists solely of uppercase letters, digits, and the
|
||||
underscore ('_') character. If the latter, you can ignore
|
||||
the warnings (B<sudo> will not complain). In B<-s> (strict)
|
||||
mode these are errors, not warnings.
|
||||
|
Reference in New Issue
Block a user