Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Connect for Kids

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 74 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       visudo [ -c ] [ -f sudoers ] [ -q ] [ -s ] [ -V ]


       visudo edits the sudoers file in a safe fashion, analogous
       to vipw(8).  visudo locks the sudoers file against multi­
       ple simultaneous edits, provides basic sanity checks, and
       checks for parse errors.  If the sudoers file is currently
       being edited you will receive a message to try again

       There is a hard-coded list of editors that visudo will use
       set at compile-time that may be overridden via the editor
       sudoers Default variable.  This list defaults to the path
       to vi(1) on your system, as determined by the configure
       script.  Normally, visudo does not honor the EDITOR or
       VISUAL environment variables unless they contain an editor
       in the aforementioned editors list.  However, if visudo is
       configured with the --with-enveditor flag or the enveditor
       Default variable is set in sudoers, visudo will use any
       the editor defines by EDITOR or VISUAL.  Note that this
       can be a security hole since it allows the user to execute
       any program they wish simply by setting EDITOR or VISUAL.

       visudo parses the sudoers file after the edit and will not
       save the changes if there is a syntax error.  Upon finding
       an error, visudo will print a message stating the line
       number(s) where the error occurred and the user will
       receive the "What now?" prompt.  At this point the user
       may enter "e" to re-edit the sudoers file, "x" to exit
       without saving the changes, or "Q" to quit and save
       changes.  The "Q" option should be used with extreme care
       because if visudo believes there to be a parse error, so
       will sudo and no one will be able to sudo again until the
       error is fixed.  If "e" is typed to edit the  sudoers file
       after a parse error has been detected, the cursor will be
       placed on the line where the error occurred (if the editor
       supports this feature).


       visudo accepts the following command line options:

       -c  Enable check-only mode.  The existing sudoers file
           will be checked for syntax and a message will be
           printed to the standard output detailing the status of
           sudoers.  If the syntax check completes successfully,
           visudo will exit with a value of 0.  If a syntax error
           is encountered, visudo will exit with a value of 1.

       -f  Specify and alternate sudoers file location.  With
           this option visudo will edit (or check) the sudoers
           file of your choice, instead of the default,

       -V  The -V (version) option causes visudo to print its
           version number and exit.


       sudoers file busy, try again later.
           Someone else is currently editing the sudoers file.

       /etc/sudoers.tmp: Permission denied
           You didn't run visudo as root.

       Can't find you in the passwd database
           Your userid does not appear in the system passwd file.

       Warning: undeclared Alias referenced near ...
           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 uppercase letters, dig­
           its, and the underscore ('_') character.  If the lat­
           ter, you can ignore the warnings (sudo will not com­
           plain).  In -s (strict) mode these are errors, not


       The following environment variables are used only if
       visudo was configured with the --with-env-editor option:

        EDITOR                 Invoked by visudo as the editor to use
        VISUAL                 Used Invoked visudo if EDITOR is not set


        /etc/sudoers           List of who can run what
        /etc/sudoers.tmp       Lock file for visudo


       Many people have worked on sudo over the years; this ver­
       sion of visudo was written by:

        Todd Miller            <Todd.Miller@courtesan.com>

       See the HISTORY file in the sudo distribution or visit
       http://www.sudo.ws/sudo/history.html for more details.


       If you feel you have found a bug in sudo, please submit a
       bug report at http://www.sudo.ws/sudo/bugs/


       Visudo is provided ``AS IS'' and any express or implied
       warranties, including, but not limited to, the implied
       warranties of merchantability and fitness for a particular
       purpose are disclaimed.  See the LICENSE file distributed
       with sudo for complete details.
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.11 Seconds