-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 create a script to kill the specific process (where the script checks, if the process to kill belongs to websphere) and define a sudo configuration to regulate access to this script.
Regards, Juergen Friedrichs PGP Fingerprint: 15B9 DF14 12EA 96C7 69F0 C509 1984 D757 4574 33EA -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.0.1 (Build 2185) iQA/AwUBQtUtRxmE11dFdDPqEQLWfQCdHeZI65yjCp706omy9Q9jKqPZm4AAn3hR ulh1N7P0cMxVn6xT4GAYZYQm =00bv -----END PGP SIGNATURE----- -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of James Melin Sent: Wednesday, July 13, 2005 4:03 PM To: [email protected] Subject: SUDO access granularity Is there any way to limit what processes someone could kill when using Sudo? Our websphere administrator wants the authority to kill a hung java thread should the need arise, and he wants the root password. I do not want to and will not give it to him. I am being directed by my management to 'just give it to him' but I really think that is an astonishingly bad idea. Is there a way to setup sudo so that if you issue a kill -9 against a thread it only allows it if the thread is owned by websphere? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
