I'm trying to install sudo on AIX 5.3. I don't have a compiler on my machine, so I was trying to find a binary. The one found at http://www.bullfreeware.com/listaix52.html that is supposed to work for 5.3 even though it was compiled on 5.2. The issue is I'm new to AIX and could not figure out how... (3 Replies)
I want give a user "sar" permission, so I modify the sudoers file: unix1 is the group for users can use sar command
Cmnd_Alias RUN_SAR = /usr/sbin/sar
User_Alias UNIX1_USERS = %unix1
UNIX1_USERS ALL = NOPASSWD:RUN_SAR
However, when I run sar command, it shows:
$ sar 1 4
sar: The... (1 Reply)
Hello,
I am logging to a server using username 'test'. I want to execute some commands as user test2.
When I am trying to run `sudo su - test2 -c 'ls'` it gives error user 'test' is not allowed to run sudo in host. But when I login into the account 'test2' using sudo su - test2 all these... (6 Replies)
I am trying to understand why I get "0" returned when I run the command sudo bootinfo -r. I know bootinfo isn't really supported in versions higher then AIX 4.2. I also know that instead of bootinfo -r I could use lsattr -El sys0 -a realmem | awk '{print $2}' and produce the same output as ... (1 Reply)
I am writing a BASH script to update a webserver and then restart Apache. It looks basically like this:
#!/bin/bash
rsync /path/on/local/machine/ foo.com:path/on/remote/machine/
ssh foo.com sudo /etc/init.d/apache2 reloadrsync and ssh don't prompt for a password, because I have DSA encryption... (9 Replies)
Does anyone have any experience using sudo to control smit on AIX 5.3?
These are the smit commands that I want certain users to execute:
# Cmnd alias specification
Cmnd_Alias SMIT = /bin/smit hacmp, \
/bin/smit pxdam, \
/bin/smit cl_lsuser, \
/bin/smit cl_users, \
/bin/smit cl_passwd
... (5 Replies)
I am planning to implement sudo for users.
Under , it looks I have to put the users who need to have sudo access:
What are the recommended for users? I don't think I need to give the ALL privilege (i.e ) to AIX users.
I'd like to know the commonly used privilege specification for sudo... (1 Reply)
Hi,
I have installed sudo on Solaris 10 (sparc). When I try to add a user I get the following:
-bash-3.00$ sudo addusr scarlet sudo
sudo: /usr/local/etc/sudoers.d is owned by uid 2, should be 0
Password:
I entered a password, thinking it was for the sudo user but it failed. Then I entered the... (3 Replies)
Hi,
I am running a remote shell from site A to site B, where both are AIX. The remote shell starts other application, and when it finishes, it returns to the site A.
The problem is that I am receiving an error signal 11 and system core error 50 - segmentation fault.
Does anyone know if there are... (6 Replies)
I cannot solve the following error bellow.
Can someone help me on this please?
Mar 31 07:08:45 serverx sudo: fork
Mar 31 07:18:50 serverx sudo: fork
Mar 31 07:28:45 serverx sudo: fork
Mar 31 07:38:47 serverx sudo: fork
Mar 31 07:48:45 serverx sudo: fork
Mar 31 07:58:45 serverx... (1 Reply)
Discussion started by: pangarano
1 Replies
LEARN ABOUT REDHAT
visudo
visudo(8) MAINTENANCE COMMANDS visudo(8)NAME
visudo - edit the sudoers file
SYNOPSIS
visudo [ -c ] [ -f sudoers ] [ -q ] [ -s ] [ -V ]
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 editors that visudo will use set at compile-time that may be overridden via the editor sudoers Default vari-
able. 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 VIS-
UAL.
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 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, @sysconfdir@/sudoers. The lock file used is the specified sudoers file with ".tmp" appended to it.
-q Enable quiet mode. In this mode details about syntax errors are not printed. This option is only useful when combined with the -c
flag.
-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 hostname or username 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.
ERRORS
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, digits, and the underscore ('_') character. If the latter, you can ignore the warnings (sudo will not complain).
In -s (strict) mode these are errors, not warnings.
ENVIRONMENT
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
FILES
/etc/sudoers List of who can run what
/etc/sudoers.tmp Lock file for visudo
AUTHOR
Many people have worked on sudo over the years; this version 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.
BUGS
If you feel you have found a bug in sudo, please submit a bug report at http://www.sudo.ws/sudo/bugs/
DISCLAIMER
Visudo is provided ``AS IS'' and any express or implied warranties, including, but not limited to, the implied warranties of merchantabil-
ity and fitness for a particular purpose are disclaimed. See the LICENSE file distributed with sudo for complete details.
CAVEATS
There is no easy way to prevent a user from gaining a root shell if the editor used by visudo allows shell escapes.
SEE ALSO vi(1), sudo(8), vipw(8).
3rd Berkeley Distribution 1.6.6 visudo(8)