Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Cannot make sudoers change work Post 302607570 by Corona688 on Wednesday 14th of March 2012 07:34:29 PM
Old 03-14-2012
Check the line closely for differences. If possible, post it literally.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to make sccs work

I am trying to use SCCS for project development . Can any one list out the basic setup nneded to be done for SCCS . I mean if I create a SCCS directory what all files to create on this . i don't have a root password of the system and I am not going to get one . I saw few post on this forum... (1 Reply)
Discussion started by: akrathi
1 Replies

2. Shell Programming and Scripting

nohup--how to make it work?

Hello gurus, I am facing an unusual problem while running nohup in shell scripts. i want to run two scripts simultaneously.In first script ,i take a backup of "nohup.out" & remove it .In second script,i state "nohup ./scriptname" but "nohup.out" is not getting generated ?? pls find attached... (1 Reply)
Discussion started by: abhijeetkul
1 Replies

3. Shell Programming and Scripting

How to make this work

Dear All, I want acces my folder that name Log , that throught /export/home/hmi/bin/log. I want direct to Log folder. When I try using alias, i'm login as root: >alias logfile='cd /export/home/hmi/bin/Log' and when I execute > logfile this is work, but after I logout and login again as... (3 Replies)
Discussion started by: heru_90
3 Replies

4. Solaris

Can't make 'set DISPLAY' to work

Hi, I used exceed and putty in the past to HP server with no problem to make 'set DISPLAY' work on my desktop. However now I have Solaris 9 on Sun server 480 and I only have putty. I can't bring the X window (eg xclock, etc) to my desktop. I tried X11Fowarding, xhost, and so on, it doesn't... (5 Replies)
Discussion started by: jr_zhang
5 Replies

5. Shell Programming and Scripting

how to make this work

hi, I have been trying to make my script work but could not, tried some of the suggestions from here but I am not getting the correct result. I have a script that was Param1 ="$1" Param2 ="$2" $Script1 log -t "$param1" "$param2" | grep operation > /dev/null || { echo "Message"... (1 Reply)
Discussion started by: rider29
1 Replies

6. UNIX for Dummies Questions & Answers

my make doesn't work

hi I wrote the following makefile, I have just one problem, when i type make clean I get the message make 'clean' is up to date and any obj file is removed from my folder, what's wrong? Thank you CC = cc all: es.o elaboration.o $(CC) -o es es.o elaboration.o elaboration.o:... (0 Replies)
Discussion started by: Puntino
0 Replies

7. Shell Programming and Scripting

How to make copy work faster

I am trying to copy a folder which contains a list of C executables. It takes 2 mins for completion,where as the entire script takes only 3 more minutes for other process. Is there a way to copy the folder faster so that the performance of the script will improve? (2 Replies)
Discussion started by: prasperl
2 Replies

8. Shell Programming and Scripting

Can't make chmod work

Can someone please help me with this I can't make it work? find /test -type f \( ! -perm -u+w -o -perm -g+w \) | egrep -v "/test/A|/test/B"|xargs chmod u+rw,g+r-w,o= I am getting error "Operation not permitted." I want to find files, exclude directory A & B and change permission on the... (2 Replies)
Discussion started by: Jang
2 Replies

9. Solaris

Make OS to look for sudoers to different path

This is for Solaris-11. We have our customize sudoers to fulfill requirements and that is placed in /usr/local/etc/. Already removed /etc/sudoers, which comes with OS default. But OS it still looking for /etc/sudoers when I give sudo command. How to make him look into /usr/local/etc ?... (7 Replies)
Discussion started by: solaris_1977
7 Replies
VISUDO(8)						       MAINTENANCE COMMANDS							 VISUDO(8)

NAME
visudo - edit the sudoers file SYNOPSIS
visudo [-chqsV] [-f sudoers] DESCRIPTION
visudo edits the sudoers file in a safe fashion, analogous to vipw(8). visudo locks the sudoers file against multiple 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 later. There is a hard-coded list of one or more editors that visudo will use set at compile-time that may be overridden via the editor sudoers Default variable. This list defaults to "/usr/bin/vi". Normally, visudo does not honor the VISUAL or EDITOR environment variables unless they contain an editor in the aforementioned editors list. However, if visudo is configured with the --with-env-editor option or the env_editor Default variable is set in sudoers, visudo will use any the editor defines by VISUAL or EDITOR. Note that this can be a security hole since it allows the user to execute any program they wish simply by setting VISUAL or EDITOR. 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). OPTIONS
visudo accepts the following command line options: -c Enable check-only mode. The existing sudoers file will be checked for syntax errors, owner and mode. A message will be printed to the standard output describing the status of sudoers unless the -q option was specified. If the check completes successfully, visudo will exit with a value of 0. If an error is encountered, visudo will exit with a value of 1. -f sudoers Specify and alternate sudoers file location. With this option visudo will edit (or check) the sudoers file of your choice, instead of the default, /etc/sudoers. The lock file used is the specified sudoers file with ".tmp" appended to it. In check- only mode only, the argument to -f may be "-", indicating that sudoers will be read from the standard input. -h The -h (help) option causes visudo to print a short help message to the standard output and exit. -q Enable quiet mode. In this mode details about syntax errors are not printed. This option is only useful when combined with the -c option. -s Enable strict checking of the sudoers file. If an alias is used before it is defined, visudo will consider this a parse error. Note that it is not possible to differentiate between an alias and a host name or user name that consists solely of uppercase letters, digits, and the underscore ('_') character. -V The -V (version) option causes visudo to print its version number and exit. ENVIRONMENT
The following environment variables may be consulted depending on the value of the editor and env_editor sudoers variables: VISUAL Invoked by visudo as the editor to use EDITOR Used by visudo if VISUAL is not set FILES
/etc/sudoers List of who can run what /etc/sudoers.tmp Lock file for visudo DIAGNOSTICS
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: {User,Runas,Host,Cmnd}_Alias referenced but not defined Either you are trying to use an undeclare {User,Runas,Host,Cmnd}_Alias or you have a user or host name listed that consists solely of uppercase letters, digits, and the underscore ('_') character. In the latter case, you can ignore the warnings (sudo will not complain). In -s (strict) mode these are errors, not warnings. Warning: unused {User,Runas,Host,Cmnd}_Alias The specified {User,Runas,Host,Cmnd}_Alias was defined but never used. You may wish to comment out or remove the unused alias. In -s (strict) mode this is an error, not a warning. Warning: cycle in {User,Runas,Host,Cmnd}_Alias The specified {User,Runas,Host,Cmnd}_Alias includes a reference to itself, either directly or through an alias it includes. This is only a warning by default as sudo will ignore cycles when parsing the sudoers file. SEE ALSO
vi(1), sudoers(5), sudo(8), vipw(8) AUTHOR
Many people have worked on sudo over the years; this version of visudo was written by: Todd Miller See the CONTRIBUTORS file in the sudo distribution (http://www.sudo.ws/sudo/contributors.html) for a list of people who have contributed to sudo. CAVEATS
There is no easy way to prevent a user from gaining a root shell if the editor used by visudo allows shell escapes. BUGS
If you feel you have found a bug in visudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/ SUPPORT
Limited free support is available via the sudo-users mailing list, see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or search the archives. DISCLAIMER
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 or http://www.sudo.ws/sudo/license.html for complete details. 1.8.5 March 14, 2012 VISUDO(8)
All times are GMT -4. The time now is 01:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy