Dear all
Ihave written a script in Hpux9.0, the ecript is working fine if I run it from root command prompt
But when I am running it thru /etc/profile or /user/.profile and login as a normal user, the owner of the process running the script is the normal user & hence cant run a root privileaged... (7 Replies)
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Hi All,
I have created an RPM installer and installed it via ROOT user & which works fine on Red Hat.
But the problem oocurs when a non root users try to run that application (from their account), it never got executed (being it has the execute permission i.e. chmod a+x somefile.sh).
I want... (6 Replies)
Hi,
I would like to know if there is anyway that I can pinpoint the user before/after he connects to the root? Also, I'm trying to find out what are the commands he inputs under root access. (6 Replies)
Hello,
can someone please provide steps, can I restrict a multiple users to only access only sftp on a server, to perform upload and download of files on their home directories.
1. I have updated their login shell as /sbin/nologin.
anything else do I need to update.
Thanks, (3 Replies)
I'm looking for a way to track commands that are run as root after a user runs sudo su - root. I have a profile set up for root that will track the commands by userid but if we change the shell it only stores it in that shells history file. (2 Replies)
Hello I have a script which is working fine so far to generate HTML file. Now i am wondering how do i include a syntax where it can change itself to root user and execute a specific commands as root user.
Please help, Thanks in advance.
-Siddhesh (2 Replies)
Hello,
I am testing sudo and I want to test it. Can anyone please let me know few commands (of course other than shutdown, reboot etc. as I can't reboot the box) on AIX that can be run by ROOT only.
Thanks
---------- Post updated at 07:43 PM ---------- Previous update was at 07:38 PM... (5 Replies)
Hi All,
I have the below requirement.
I want to copy the local file to remote after that i need to run the local script on a remote machine.When i use two ssh commnds i can achieve this. But i want to achieve this using one ssh command.
Below command to copy the local file to remote
ssh -q... (2 Replies)
Discussion started by: mohanalakshmi
2 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)