Use 8 and 5 instead of @mansectsu@ and @mansectform@ since the latter

confuses pod2man.  The Makefile rules for the .man.in file will add
@mansectsu@ and @mansectform@ back in after pod2man is done anyway.

diff --git a/sudo.pod b/sudo.pod
index 81a48cb57a84b62bb09ff5f078e0640ad3c882dc..485d992cefc0ee4711919f62931beccb77a815f3 100644 (file)
--- a/sudo.pod
+++ b/sudo.pod
@@ -117,7 +117,7 @@ standard input, standard output and standard error.  The B<-C>
 above the standard error (file descriptor three).  Values less than
 three are not permitted.  This option is only available if the
 administrator has enabled the I<closefrom_override> option in
-L<sudoers(@mansectform@)>.
+L<sudoers(5)>.
 
 =item -c
 
@@ -135,9 +135,9 @@ where B<sudo> has been configured with the --with-logincap option.
 =item -E
 
 The B<-E> (I<preserve environment>) option will override the
-I<env_reset> option in L<sudoers(@mansectform@)>).  It is only
+I<env_reset> option in L<sudoers(5)>).  It is only
 available when either the matching command has the C<SETENV> tag
-or the I<setenv> option is set in L<sudoers(@mansectform@)>.
+or the I<setenv> option is set in L<sudoers(5)>.
 
 =item -e
 
@@ -179,8 +179,8 @@ temporary file.
 
 The B<-H> (I<HOME>) option sets the C<HOME> environment variable
 to the homedir of the target user (root by default) as specified
-in passwd(@mansectform@).  By default, B<sudo> does not modify C<HOME>
-(see I<set_home> and I<always_set_home> in L<sudoers(@mansectform@)>).
+in passwd(5).  By default, B<sudo> does not modify C<HOME>
+(see I<set_home> and I<always_set_home> in L<sudoers(5)>).
 
 =item -h
 
@@ -189,7 +189,7 @@ The B<-h> (I<help>) option causes B<sudo> to print a usage message and exit.
 =item -i
 
 The B<-i> (I<simulate initial login>) option runs the shell specified
-in the L<passwd(@mansectform@)> entry of the user that the command is
+in the L<passwd(5)> entry of the user that the command is
 being run as.  The command name argument given to the shell begins
 with a `C<->' to tell the shell to run as a login shell.  B<sudo>
 attempts to change to that user's home directory before running the
@@ -277,7 +277,7 @@ the standard input instead of the terminal device.
 
 The B<-s> (I<shell>) option runs the shell specified by the I<SHELL>
 environment variable if it is set or the shell as specified
-in L<passwd(@mansectform@)>.
+in L<passwd(5)>.
 
 =item -U
 
@@ -291,7 +291,7 @@ option.
 The B<-u> (I<user>) option causes B<sudo> to run the specified command
 as a user other than I<root>.  To specify a I<uid> instead of a
 I<username>, use I<#uid>.  Note that if the I<targetpw> Defaults
-option is set (see L<sudoers(@mansectform@)>) it is not possible
+option is set (see L<sudoers(5)>) it is not possible
 to run commands with a uid not listed in the password database.
 
 =item -V
@@ -323,7 +323,7 @@ command line are subject to the same restrictions as normal environment
 variables with one important exception.  If the I<setenv> option
 is set in I<sudoers> or the command to be run has the C<SETENV> tag
 set the user may set variables that would overwise be forbidden.
-See L<sudoers(@mansectform@)> for more information.
+See L<sudoers(5)> for more information.
 
 =head1 RETURN VALUES
 
@@ -412,7 +412,7 @@ editors).  Because of this, care must be taken when giving users
 access to commands via B<sudo> to verify that the command does not
 inadvertently give the user an effective root shell.  For more
 information, please see the C<PREVENTING SHELL ESCAPES> section in
-L<sudoers(@mansectform@)>.
+L<sudoers(5)>.
 
 =head1 ENVIRONMENT
 
@@ -454,7 +454,7 @@ B<sudo> utilizes the following environment variables:
 
 =head1 EXAMPLES
 
-Note: the following examples assume suitable L<sudoers(@mansectform@)> entries.
+Note: the following examples assume suitable L<sudoers(5)> entries.
 
 To get a file listing of an unreadable directory:
 
@@ -481,8 +481,8 @@ to make the C<cd> and file redirection work.
 
 =head1 SEE ALSO
 
-L<grep(1)>, L<su(1)>, L<stat(2)>, L<login_cap(3)>, L<passwd(@mansectform@)>,
-L<sudoers(@mansectform@)>, L<visudo(@mansectsu@)>
+L<grep(1)>, L<su(1)>, L<stat(2)>, L<login_cap(3)>, L<passwd(5)>,
+L<sudoers(5)>, L<visudo(8)>
 
 =head1 AUTHORS
 
@@ -502,7 +502,7 @@ if that user is allowed to run arbitrary commands via B<sudo>.
 Also, many programs (such as editors) allow the user to run commands
 via shell escapes, thus avoiding B<sudo>'s checks.  However, on
 most systems it is possible to prevent shell escapes with B<sudo>'s
-I<noexec> functionality.  See the L<sudoers(@mansectform@)> manual
+I<noexec> functionality.  See the L<sudoers(5)> manual
 for details.
 
 It is not meaningful to run the C<cd> command directly via sudo, e.g.,

diff --git a/sudoers.pod b/sudoers.pod
index 7ffb752e09b2ce94e6adf3da3f09a067054b745f..2e5332c567bcce3094c329a6edefefb6c9e75682 100644 (file)
--- a/sudoers.pod
+++ b/sudoers.pod
@@ -1363,7 +1363,7 @@ B<sudoedit>.
 
 =head1 SEE ALSO
 
-L<rsh(1)>, L<su(1)>, L<fnmatch(3)>, L<sudo(@mansectsu@)>, L<visudo(@mansectsu@)>
+L<rsh(1)>, L<su(1)>, L<fnmatch(3)>, L<sudo(8)>, L<visudo(8)>
 
 =head1 CAVEATS
 

diff --git a/visudo.pod b/visudo.pod
index 4bd518b84512dfa182e51f43d6b92e3e1ac51ec5..8bd1fd329f25ed67ca517b967b38378854ad2a95 100644 (file)
--- a/visudo.pod
+++ b/visudo.pod
@@ -32,7 +32,7 @@ B<visudo> [B<-c>] [B<-q>] [B<-s>] [B<-V>] [B<-f> I<sudoers>]
 =head1 DESCRIPTION
 
 B<visudo> edits the I<sudoers> file in a safe fashion, analogous to
-L<vipw(@mansectsu@)>.  B<visudo> locks the I<sudoers> file against multiple
+L<vipw(8)>.  B<visudo> locks the I<sudoers> file against multiple
 simultaneous edits, provides basic sanity checks, and checks
 for parse errors.  If the I<sudoers> file is currently being
 edited you will receive a message to try again later.
@@ -153,7 +153,7 @@ B<-s> (strict) mode this is an error, not a warning.
 
 =head1 SEE ALSO
 
-L<vi(1)>, L<sudoers(@mansectform@)>, L<sudo(@mansectsu@)>, L<vipw(@mansectsu@)>
+L<vi(1)>, L<sudoers(5)>, L<sudo(8)>, L<vipw(8)>
 
 =head1 AUTHOR