I'm trying to provide "/usr/bin/kill -HUP" command to one of the user using sudo file. I have configured sudo as following:
When I login as the user and execute 'sudo -l' command, it is showing errors and the user is saying it is prompting for password. Any idea how kill -HUP can be configured in sudo?
Last edited by pludi; 05-11-2010 at 01:40 AM..
Reason: code tags, please...
folks;
How can i give a group a sudo permission to execute only some command "like start/stop Apache", so every user in that group can sudo to use this as himself, i mean when he tries to sudo, he will be asked for a password (and make it so he must use his own NT password not a generic one) then... (6 Replies)
HI friends can i know how to assign sudo permission to normal user in solaris, and if not i want to assign few commands like format,user creation to normal user, i want to share few permission to normal user towork like a root in $ prompt. (2 Replies)
All:
I'm having a problem with sudo on Solaris 5.10 that is giving me fits (and BTW, I'm a Linux admin by trade...).
The issue is that I have a number of users (myself included) that cannot sudo to root to complete user admin tasks. Assuming the user is jdoe, and the group with the elevated... (3 Replies)
Hi all,
I have to grant sudo permission to a user.
I have searched online and find that /etc/sudoers file needs to be changed with visudo command. As i am new to linux, this is not clear to me. Can anybody take an example and show me how exactly this done.
Thanks in advance! (2 Replies)
Hi All
I had installed sudo in HP UX 11.3 and it is working fine but not able to make entry required to set permission similar to ROOT without using password (PASSWD) change option for define user in /etc/sudoers file
Please help if some know the syntex? :confused::wall: (2 Replies)
I'm on AIX. I have triggered an infinite loop process (to keep looking for input file availability for further process). At present only I can kill the process.
In case my colleague wants to kill the process for any reason, how do I provide permission to others to kill the process?
Currently... (3 Replies)
I have a script that checks if the script has been ran with sudo.
If the script is not ran as sudo, the current script is being executed with exec sudo bash.
You are asked for a password, you type in the password, success. Everything is perfect - the commands inside the script are ran as sudo.... (1 Reply)
<?php
$comando = "kill -9 3104";
$output = shell_exec($comando);
?>
I am running this web page, but it does not execute the command, in the log file it looks like this:
sh: 1: kill: Operation not permitted
How do I give permission to execute the command? (1 Reply)
Discussion started by: Rodrigo_Bueno
1 Replies
LEARN ABOUT DEBIAN
gksu
GKSU(1) User Commands GKSU(1)NAME
gksu - GTK+ frontend for su and sudo
SYNOPSIS
gksu
gksu [-u <user>] [options] <command>
gksudo [-u <user>] [options] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
Notice that all the magic is done by the underlying library, libgksu. Also notice that the library will decide if it should use su or sudo
as backend using the /apps/gksu/sudo-mode gconf key, if you call the gksu command. You can force the backend by using the gksudo command,
or by using the --sudo-mode and --su-mode options.
If no command is given, the gksu program will display a small window that allows you to type in a command to be run, and to select what
user the program should be run as. The other options are disregarded, right now, in this mode.
OPTIONS --debug, -d
Print information on the screen that might be useful for diagnosing and/or solving problems.
--user <user>, -u <user>
Call <command> as the specified user.
--disable-grab, -g
Disable the "locking" of the keyboard, mouse, and focus done by the program when asking for password.
--prompt, -P
Ask the user if they want to have their keyboard and mouse grabbed before doing so.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
--login, -l
Make this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display!
--description <description|file>, -D <description|file>
Provide a descriptive name for the command to be used in the default message, making it nicer. You can also provide the absolute
path for a .desktop file. The Name key for will be used in this case.
--message <message>, -m <message>
Replace the standard message shown to ask for password for the argument passed to the option. Only use this if --description does
not suffice.
--print-pass, -p
Ask gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--su-mode, -w
Force gksu to use su(1) as its backend for running the programs.
--sudo-mode, -S
Force gksu to use sudo(1) as its backend for running the programs.
SEE ALSO su(1), sudo(1)gksu version 2.0.x August 2006 GKSU(1)