If the process is not a zombie this will work.
Get the pid of the process then pretend the result is 1234
Code:
kill 1234
Some other folks may suggest kill -9 [pid]. This is a bad idea and is a last resort. Why?
kill -9 prevents the process from cleaning up, assuming it is a reasonable unix application. This may leave some file, a semaphore, or some other object in a bad state, such that the application may fail next time.
Hello guys,
I have a process named monitoreo, with 'monitoreo start' my process start until i kill them, now i want to do 'monitoreo stop' to kill them.
After 'monitoreo start' i have this process running:
ps -af
UID PID PPID C STIME TTY TIME CMD
ati 10958 1495 ... (5 Replies)
Hi guys,
I'm writing a script in which I have to get file from a remote host by ftp. The problem is that the remote machine could be very slow, not connected or ok. To resolve this problem, I write this:
echo "verbose on" > ftprap.cmd
echo "prompt " >> ftprap.cmd
echo "ascii"... (3 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 Expert,
I am not able to kill certain user process as root. I have tried using:
pkill -u uname
skill KILL -u uname
kill -9 PID
*** I have not using killall yet, since this server has more than 100 users online atm.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND... (1 Reply)
Hello Everyone,
I have a process that should be always running. Unfortunately, this process is getting down almost every 10 minutes. I want to make a script that verify the state of this process: If the process is up, the script shouldn't do nothing and if it's down he should run it.
Can... (3 Replies)
Hi All ,
There always exist one process in hold state every day which will cause savior impact if i didn't kill it.
i will do it manually . Manul process is this.
sudo -iu root/opt/app/root/cdlinux/ndm/bin/direct -- it will take me connect direct prompt
Sel proc ; -- it will displays... (9 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
LEARN ABOUT ULTRIX
kill
kill(2) System Calls Manual kill(2)Name
kill - send signal to a process
Syntax
#include <sys/types.h>
#include <signal.h>
kill(pid, sig)
pid_t pid;
int sig;
Description
The system call sends the signal sig to a process specified by the process number pid. The sig can be a signal specified in a call or it
can be 0. If the sig is 0, error checking is performed, but a signal is not sent. This call can be used to check the validity of pid.
The sending and receiving processes must have the same effective user ID, otherwise this call is restricted to the superuser with the
exception of the signal SIGCONT. The signal SIGCONT can always be sent to a child or grandchild of the current process.
If the process number is 0, the signal is sent to all other processes in the sender's process group.
If the process number is negative but not -1, the signal is sent to all processes whose process-group-id is equal to the absolute value of
the process number.
The above two options are variants of
If the process number is -1, and the user is the superuser, the signal is broadcast for all processes except to system processes and the
process sending the signal.
Processes may send signals to themselves.
Environment
System Five
POSIX
When your program is compiled in the System V or POSIX environment, a signal is sent if either the real or effective uid of the sending
process matches the real or saved-set-uid (as described in ) of the receiving process. In addition, any process can use a pid of -1, and
the signal is sent to all processes subject to these permission checks.
In POSIX mode, the pid argument is of type pid_t.
Return Values
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned, and is set to indicate the error.
Diagnostics
The system call fails under the following conditions:
[EINVAL] The sig is not a valid signal number.
[EPERM] The sending process is not the superuser, and its effective user ID does not match the effective user ID of the receiving
process.
[ESRCH] No process can be found corresponding to that specified by pid.
See Alsoexecve(2), getpgrp(2), getpid(2), killpg(2), sigvec(2), pause(3)kill(2)