set head off
set feed off
set verify off
select ssn.process as client_process_id, pcs.spid as oracle_process_id
from v$session ssn inner join v$process pcs on (pcs.addr = ssn.paddr)
where ssn.module = 'MARC_RFD248';
Note that the above script would work only if it is the owner of the process that it is killing. If not, then it cannot kill. Then you would have to use root or any other superuser.
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)
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)
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
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)
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)
Hi!
I need your help, please.
I'm in AIX node and sometimes listener process from an oracle instance gets duplicated, i mean that it get spawned a second listener process. As we can't apply changes to the databases on this months, i want to build a shell that can identify the second... (6 Replies)
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)
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
LEARN ABOUT BSD
kill
KILL(1) General Commands Manual KILL(1)NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO csh(1), ps(1), kill(2), sigvec(2)BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)