Sponsored Content
Operating Systems AIX How to allow group members to kill process? Post 302272676 by The Dark Knight on Wednesday 31st of December 2008 10:15:48 AM
Old 12-31-2008
Quote:
Originally Posted by bakunin
You cannot - not directly, that is - allow group members to kill other users processes. A user kann only kill his own processes, only root (more exactly: any user with uid 0) is allowed to kill any process.

You could create a workaround by using sudo: create a script which checks the group memberships of originator and process in question and which kills the process accordingly. Let this script run with root authority and use sudo to authenticate its use.

I hope this helps.

bakunin

Thanks for your help but i have another solution already
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

listing members of a unix group

I know there is a "groups" command to list the groups a user belongs to, but how about the opposite? Is there a standard command to find out which users belong to a particular group? (2 Replies)
Discussion started by: ovaska
2 Replies

2. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

3. Solaris

make issue when I add some members into a NIS group on solaris 9,please help !!

Hello Sir, I want to add some members into a group on NIS domain, but when I run "/usr/ccs/bin/make group" to update the group map it was failed :-( the error message is : problem storing develop... (4 Replies)
Discussion started by: lk74612
4 Replies

4. Programming

allowing members of a group to kill a process

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

5. Shell Programming and Scripting

How to get a list of group members?

Is there a command to get a list of group members? Something similar to the groups command, but instead of passing a username and returning groups, you pass it a groupname, and it returns members? It is difficult to do it manually because the group membership information is split across two... (5 Replies)
Discussion started by: akbar
5 Replies

6. Shell Programming and Scripting

how to kill a process initiated by other user at the same group

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 a group members to be able to kill (using kill command) processes created by other user at the same group? and i need the change to be at the script... (5 Replies)
Discussion started by: The Dark Knight
5 Replies

7. Linux

members in a group

Hi all, I am new to Linux.Can anyone tell me how to display or list all the members in a group? Thanks in advance. (9 Replies)
Discussion started by: arthi
9 Replies

8. Solaris

How to list group members in solaris 9

Hi, I already gone through with old post regarding listing the group members and tried the command getenv group other the result is other::1:root i listed my part of the /etc/passwd file below test1:x:100:1::/home/test1:/bin/sh test2:x:101:1::/home/test2:/bin/ksh... (7 Replies)
Discussion started by: vr_mari
7 Replies

9. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies

10. UNIX for Advanced & Expert Users

Setfacl and granting permissions to a group and its members on a directory

Hi! I created a group HACKERS and made the user "demo" its member. $ id demo uid=500(demo) gid=500(demo) groups=500(demo),502(HACKERS) $ Next, I granted read and execute permissions to the group "HACKERS" on /var/log/httpd as shown below: setfacl -m "g:HACKERS:r-x"... (2 Replies)
Discussion started by: indiansoil
2 Replies
kill(2) 							System Calls Manual							   kill(2)

NAME
kill - Sends a signal to a process or to a group of processes SYNOPSIS
#include <signal.h> int kill( pid_t process, int signal ); Application developers may want to specify an #include statement for <sys/types.h> before the one for <signal.h> if programs are being developed for multiple platforms. The additional #include statement is not required on Tru64 UNIX systems or by ISO or X/Open standards, but may be required on other vendors' systems that conform to these standards. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: kill(): XSH5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
Specifies the process or group of processes. Specifies the signal. If the signal parameter is a value of 0 (the null signal), error check- ing is performed but no signal is sent. This can be used to check the validity of the process parameter. DESCRIPTION
The kill() function sends the signal specified by the signal parameter to the process or group of processes specified by the process param- eter. To send a signal to another process, at least one of the following must be true: The real or the saved set-user-ID of the sending process matches the real or effective user ID of the receiving process. The process is trying to send the SIGCONT signal to one of its session's processes. The calling process has root privileges. Processes can send signals to themselves. Sending a signal does not imply that the operation is successful. All signal operations must pass the access checks prescribed by each enforced access control policy on the system. If the process parameter is greater than 0 (zero), the signal specified by the signal parameter is sent to the process that has a process ID equal to the value of the process parameter. If the process parameter is equal to 0 (zero), the signal specified by the signal parameter is sent to all of the processes (other than system processes) whose process group ID is equal to the process group ID of the sender. If the process parameter is equal to -1, the signal specified by the signal parameter is sent to all of the processes other than system processes for which the process has permission to send that signal. For example, if the effective user ID of the sender has root privi- leges, the signal specified by the signal parameter is sent to all of the processes other than system processes. If the process parameter is negative but not -1, the signal specified by the signal parameter is sent to all of the processes which have a process group ID equal to the absolute value of the process parameter. RETURN VALUES
Upon successful completion, the kill() function returns a value of 0 (zero). Otherwise, a value of -1 is returned and errno is set to indi- cate the error. NOTES
Some applications and scripts depend on the process ID of the init program being 1 (one): do not depend on it. Instead, use standard methods, such as the ps and grep commands, to obtain all process IDs. ERRORS
The kill() function sets errno to the specified values for the following conditions: The signal parameter is not a valid signal number. [Tru64 UNIX] The signal parameter is SIGKILL, SIGSTOP, SIGTSTP or SIGCONT and the process parameter is the process ID of the init program. No process or process group can be found corresponding to that specified by the process parameter. The real or saved user ID does not match the real or effective user ID of the receiving process, the calling process does not have appropriate privilege, and the process is not sending a SIGCONT signal to one of its session's processes. [Tru64 UNIX] The calling process does not have appropriate privilege. RELATED INFORMATION
Functions: getpid(2), killpg(2), raise(3), setpgid(2), sigaction(2), sigvec(2) Standards: standards(5) delim off kill(2)
All times are GMT -4. The time now is 11:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy