1. Download the rpm file needed to install the sudoers package in AIX AIX open sources rpms
Search for the file sudo-1.6.7p5-3.aix5.1.ppc.rpm and download it
2. Copy the downloaded file to the AIX servers /tmp/SUDO directory
3. change the permission to chmod 777 <Filename>
4.smitty install-> Install and Update Software-> Install Software-->INPUT device / directory for software [.]#current directory
SOFTWARE to install (Press Esc+F4 which displays the rpm file in the directory)
ACCEPT new license agreements? Yes
and press enter to install the rpm File on your machine
5. Configuring logs for Sudo
----------------------------------------------------------------------------------------------------
6.Enter visudo command to view and putting an entry of the users in the /etc/sudoers quit it by saving it.
7. Login into the userlogin by opening a duplicate session of su <user name> and enter sudo -s for sudo -s login credentials.
8. Finally check the log file
This is the way to use the sudoers in AIX.
Last edited by pludi; 05-25-2010 at 08:33 AM..
Reason: added code tags, removed self-promotion
I am in need some some simple... straight forward instructions for creating file systems on AIX.
I have a raid controller and 4 18.2gb Hot Swap SCSI drives.
I am sooooo confused about Volume Groups, Physical Volume, and Physical Partition, and Logical Volume and Logical Partitions.
In a... (1 Reply)
hey all
I have ibm RS6000 WORKSTATION,iam new to aix i worked on sparc system,but dont know anything abt aix can some one guide me how to install aix 4.3.3 fresh installtion how the partition to be created how to start the installltion and finish it how to add new external hdd. plss osme one... (1 Reply)
Hi,
I'm facing troubles in installing MySQL on AIX 5.3. After I run make it's getting errors and exiting, few of the errors are pasted below. Please help me to install it succesfully.
ld: 0711-235 WARNING: Archive member ../mysys/libmysys.a is not
an object file or an import list.... (2 Replies)
This is a serious longshot but my system crashed and I need to bring it back up, I put my cd into the drive to boot and it does not work. I cannot find another copy anywhere (internet, friends, other companies, etc...). Apparently while trying to install the Veristas remote agent for unix I... (0 Replies)
Hi,
How can I undo installation of a package on AIX 4.3 properly?
It's an install script. On linux, I usually just kill the process and delete from disk with this command "find .... exec rm -r {}\;". And it usually works. Can I do the same with AIX 4.3?
Thanks,
Itik (2 Replies)
Hi all
I'm newbie
In this forum, i have posted some topics about zip and unzip a file on AIX system.
And i have some answers so that AIX can not work with zip file, and they tell me some files to zip and unzip my files on AIX such as:
zip-2.3-3.aix4.3.ppc.rpm
unzip-5.51-1.aix5.1.ppc.rpm... (2 Replies)
Dear All,
I heard about munin tool features and am planning to get exposure in order to monitor my environment through munin. Basically my environment is having 18 AIX servers (Version is AIX 5.3) and am not able to monitor actively CPU, DISK, Memory utilizations. If I want to install Munin in... (1 Reply)
Could you please let me know, if it is possible to have NIM server running on one volume group and other applications like oracle running on other volume group. Do we need to have a dedicated server for only AIX NIM server?. I am new to AIX and planning to install NIM server on a test server. which... (3 Replies)
Hi There
I am trying to install AIX6.1 from a NIM server, but the installation hangs on 90% Filesets processed 551 of 571.
Is there some log somewhere to check why it is failing or hanging?
I have done it before successfully, with the same spot and lpp_source.
I am new to AIX and... (7 Replies)
Hi all,
I'm trying to setup my sudoer file at work to have the right security, but I'm not able to refine to the level I want.
Here's what I would like to have:
=> OS Users
- John (group staff)
- Bob (group staff)
- app20adm (group app20grp)
- app70adm (group app70grp)
- sys20adm... (0 Replies)
Discussion started by: victorbrca
0 Replies
LEARN ABOUT CENTOS
visudo
VISUDO(8) BSD System Manager's Manual 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/local/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).
The options are as follows:
-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 settings:
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 user ID 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 undeclared {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)AUTHORS
Many people have worked on sudo over the years; this version consists of code written primarily by:
Todd C. Miller
See the CONTRIBUTORS file in the sudo distribution (http://www.sudo.ws/sudo/contributors.html) for an exhaustive list of people who have con-
tributed 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.
Sudo 1.8.6p7 July 12, 2012 Sudo 1.8.6p7