12-31-2008
Quote:
Originally Posted by
matrixmadhan
Say,
if a process is kicked off by user_A, it will run as user_A ( group grp_A for example )
and a user user_B from the same group grp_A cannot kill that process assuming there is no sudo root privs to the user user_B and this operation will not be permitted by kernel.
So, what can be done is create a common user id : common_user_testing and this user_id to be shared for creating processes which means that user_A can kickstart that and user_B can kill that.
Thanks for your advise
Actually I used something close to what you said
I created an (Execute Only) Script that switches to common user and call the script that creates the process then switch back to the main user, and the same happens when i want to kill the process
Thanks for you Advise, I t was helpful
10 More Discussions You Might Find Interesting
1. Programming
I've written a python program where I want to allow members of a specific group the ability to kill it, and I'm not sure how to do it. I've been looking at the setuid() and setgid() and similar functions in the os module, but haven't been able to get them to work. I can't seem to change the uid or... (1 Reply)
Discussion started by: vastcharade
1 Replies
2. Shell Programming and Scripting
To all,
I need to find a group in /etc/group and if found, I need to list out all the login ids for that group - one login id per line.
To find the list of user login ids for group X, I probably will use
cat /etc/group|grep ^X:|cut -d: -f4
This will return back a list of comma delimited... (4 Replies)
Discussion started by: april
4 Replies
3. Shell Programming and Scripting
Hi,
I scheduled one script through crontab command and seems like it is hanging. I come to know this through the command 'ps -ef' whcih is showing me the program running, but no chances of it to take more than 2hrs to comlpete.
I want to kill that process. I tried to kill it using the... (6 Replies)
Discussion started by: DILEEP410
6 Replies
4. AIX
Hey
I'm writing a script that creates some processes,and some scripts which kill those processes.
the question is Simply:
How can I allow group members to be able to kill processes created by other member at the same group?
I need your help as soon as possible
Thanks for your help in... (4 Replies)
Discussion started by: The Dark Knight
4 Replies
5. UNIX for Dummies Questions & Answers
I am looking for a way to kill 2 processes from a user through some kind of script.
Using an oracle script, I get two process ids that need to be killed.
SQL> select ssn.process as client_process_id, pcs.spid as oracle_process_id, ssn.sid, ssn.serial#
2 from v$session ssn inner join... (5 Replies)
Discussion started by: Meert
5 Replies
6. UNIX for Dummies Questions & Answers
how to kill all the "netsacpe" processes of a particular user? (1 Reply)
Discussion started by: karthi_g
1 Replies
7. Shell Programming and Scripting
Hi Here is my problem:
1)I am login to unix server through my login id and do SU - xxx
2) Start the script which is running in background
I want that other user which login to there id and do SU - yyy(Different user) kill that
script.
Could you please help me in this. (9 Replies)
Discussion started by: mr_harish80
9 Replies
8. UNIX for Advanced & Expert Users
How can I kill a process owned by user1? I will be using another user (user2) (not root) and we are on the same primary and secondary group. I copied everything including it's .profile and set the path accordingly.
user1@hostnmae0:/home/user1 $ pkill java
pkill: Failed to signal pid 1234:... (2 Replies)
Discussion started by: lhareigh890
2 Replies
9. Shell Programming and Scripting
Hi folks,
I want to kill all process of oracle user and won't kill shell, should i try this? Please confirm.
1st way
pgrep -u oracle | sudo xargs kill -9
2nd way
killall -u oracle (2 Replies)
Discussion started by: learnbash
2 Replies
10. UNIX for Beginners Questions & Answers
the task is grant user1 to kill another (for example user2) process. My steps:
by root:
usermod -P "Process Management" user1
login user1
user1@server (~) pfexec kill <PID>
the result is:
ksh: <PID>: not found
or user1@server (~) pfexec pkill <PID>
the result: nothing happens, still... (0 Replies)
Discussion started by: dsyberia
0 Replies
KILL(1) User Commands KILL(1)
NAME
kill - terminate a process
SYNOPSIS
kill [-s signal|-p] [-q sigval] [-a] [--] pid...
kill -l [signal]
DESCRIPTION
The command kill sends the specified signal to the specified process or process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal. For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather similar to that of the command described here. The '-a' and '-p'
options, and the possibility to specify processes by command name are a local extension.
If sig is 0, then no signal is sent, but error checking is still performed.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid can be one of five things:
n where n is larger than 0. The process with pid n will be signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group n are signaled. When an argument of the form '-n' is given, and it
is meant to denote a process group, either the signal must be specified first, or the argument must be preceded by a '--'
option, otherwise it will be taken as the signal to send.
commandname
All processes invoked using that name will be signaled.
-s, --signal signal
Specify the signal to send. The signal may be given as a signal name or number.
-l, --list [signal]
Print a list of signal names, or convert signal given as argument to a name. The signals are found in /usr/include/linux/signal.h
-L, --table
Similar to -l, but will print signal names and their corresponding numbers.
-a, --all
Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.
-p, --pid
Specify that kill should only print the process id (pid) of the named processes, and not send any signals.
-q, --queue sigval
Use sigqueue(2) rather than kill(2) and the sigval argument is used to specify an integer to be sent with the signal. If the
receiving process has installed a handler for this signal using the SA_SIGINFO flag to sigaction(2), then it can obtain this data
via the si_value field of the siginfo_t structure.
NOTES
It is not possible to send a signal to explicitly selected thread in a multithreaded process by kill(2) syscall. If kill(2) is used to
send a signal to a thread group, then kernel selects arbitrary member of the thread group that has not blocked the signal. For more
details see clone(2) CLONE_THREAD description.
The command kill(1) as well as syscall kill(2) accepts TID (thread ID, see gettid(2)) as argument. In this case the kill behavior is not
changed and the signal is also delivered to the thread group rather than to the specified thread.
SEE ALSO
bash(1), tcsh(1), kill(2), sigvec(2), signal(7)
AUTHOR
Taken from BSD 4.4. The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.
AVAILABILITY
The kill command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils/util-
linux/>.
util-linux March 2013 KILL(1)