1 .\" DO NOT EDIT THIS FILE, IT IS NOT THE MASTER!
2 .\" IT IS GENERATED AUTOMATICALLY FROM visudo.mdoc.in
4 .\" Copyright (c) 1996,1998-2005, 2007-2012
5 .\" Todd C. Miller <Todd.Miller@courtesan.com>
7 .\" Permission to use, copy, modify, and distribute this software for any
8 .\" purpose with or without fee is hereby granted, provided that the above
9 .\" copyright notice and this permission notice appear in all copies.
11 .\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
12 .\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
13 .\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
14 .\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
15 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
16 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
17 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
18 .\" ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
20 .\" Sponsored in part by the Defense Advanced Research Projects
21 .\" Agency (DARPA) and Air Force Research Laboratory, Air Force
22 .\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
24 .TH "VISUDO" "@mansectsu@" "June 12, 2013" "Sudo @PACKAGE_VERSION@" "System Manager's Manual"
29 \- edit the sudoers file
34 [\fB\-f\fR\ \fIsudoers\fR]
39 file in a safe fashion, analogous to
44 file against multiple simultaneous edits, provides basic sanity checks,
45 and checks for parse errors.
48 file is currently being edited you will receive a message to try again later.
50 There is a hard-coded list of one or more editors that
52 will use set at compile-time that may be overridden via the
65 environment variables unless they contain an editor in the aforementioned
69 is configured with the
70 \fR--with-env-editor\fR
77 will use any the editor defines by
81 Note that this can be a security hole since it allows the user to
82 execute any program they wish simply by setting
90 file after the edit and will
91 not save the changes if there is a syntax error.
92 Upon finding an error,
94 will print a message stating the line number(s)
95 where the error occurred and the user will receive the
98 At this point the user may enter
104 to exit without saving the changes, or
106 to quit and save changes.
109 option should be used with extreme care because if
111 believes there to be a parse error, so will
116 again until the error is fixed.
121 file after a parse error has been detected, the cursor will be placed on
122 the line where the error occurred (if the editor supports this feature).
124 The options are as follows:
133 checked for syntax errors, owner and mode.
134 A message will be printed to the standard output describing the status of
138 option was specified.
139 If the check completes successfully,
141 will exit with a value of 0.
142 If an error is encountered,
144 will exit with a value of 1.
146 \fB\-f\fR \fIsudoers\fR
153 will edit (or check) the
156 instead of the default,
157 \fI@sysconfdir@/sudoers\fR.
158 The lock file used is the specified
165 mode only, the argument to
171 will be read from the standard input.
175 \fB\-h\fR (\fIhelp\fR)
178 to print a short help message
179 to the standard output and exit.
185 In this mode details about syntax errors are not printed.
186 This option is only useful when combined with
197 If an alias is used before it is defined,
199 will consider this a parse error.
200 Note that it is not possible to differentiate between an
201 alias and a host name or user name that consists solely of uppercase
202 letters, digits, and the underscore
208 \fB\-V\fR (\fIversion\fR)
211 to print its version number
214 The following environment variables may be consulted depending on
235 \fI@sysconfdir@/sudoers\fR
236 List of who can run what
238 \fI@sysconfdir@/sudoers.tmp\fR
242 \fRsudoers file busy, try again later.\fR
243 Someone else is currently editing the
247 \fR@sysconfdir@/sudoers.tmp: Permission denied\fR
252 \fRCan't find you in the passwd database\fR
253 Your user ID does not appear in the system passwd file.
255 \fRWarning: {User,Runas,Host,Cmnd}_Alias referenced but not defined\fR
256 Either you are trying to use an undeclared {User,Runas,Host,Cmnd}_Alias
257 or you have a user or host name listed that consists solely of
258 uppercase letters, digits, and the underscore
261 In the latter case, you can ignore the warnings
267 (strict) mode these are errors, not warnings.
269 \fRWarning: unused {User,Runas,Host,Cmnd}_Alias\fR
270 The specified {User,Runas,Host,Cmnd}_Alias was defined but never
272 You may wish to comment out or remove the unused alias.
275 (strict) mode this is an error, not a warning.
277 \fRWarning: cycle in {User,Runas,Host,Cmnd}_Alias\fR
278 The specified {User,Runas,Host,Cmnd}_Alias includes a reference to
279 itself, either directly or through an alias it includes.
280 This is only a warning by default as
282 will ignore cycles when parsing
288 sudoers(@mansectform@),
292 Many people have worked on
294 over the years; this version consists of code written primarily by:
300 See the CONTRIBUTORS file in the
302 distribution (http://www.sudo.ws/sudo/contributors.html) for an
303 exhaustive list of people who have contributed to
306 There is no easy way to prevent a user from gaining a root shell if
309 allows shell escapes.
311 If you feel you have found a bug in
313 please submit a bug report at http://www.sudo.ws/sudo/bugs/
315 Limited free support is available via the sudo-users mailing list,
316 see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or
322 and any express or implied warranties, including, but not limited
323 to, the implied warranties of merchantability and fitness for a
324 particular purpose are disclaimed.
325 See the LICENSE file distributed with
327 or http://www.sudo.ws/sudo/license.html for complete details.