|
|
Sponsored Content
Operating Systems
OS X (Apple)
The Great Hopping Unkillable PID
Post 302909014 by Don Cragun on Sunday 13th of July 2014 03:11:45 PM
07-13-2014
| Moderator's Comments: | ||
|
To expand on what bartus11 said, kill and killall are designed to send a signal to one or more running processes. They are failing for you because the processes you're trying to kill are already gone when you are trying to kill them.
It sounds like your VLC processes are starting and dying very quickly and whatever parent process started them sees that they failed and is restarting them in an endless loop. You need to kill the process that is starting them AND THEN you need to find out why they are dying instead of doing whatever they are supposed to do.
If you use ps -fax (instead of ps -ax), you'll see a column with the header PPID. That column shows the parent process ID of the process identified by that line. If the PIDs are going up by 3 on each cycle, you may have a case where you have a parent, child, and grandchild. If that is the case, you'll need to find the PPID of the PPID.
However, if the PPID is 1; do not try to kill that PID. It means that the parent of your VLC process died after starting the VLC process. You need to find the intermediate process that started your VLC process before it dies and then find its parent.
This User Gave Thanks to Don Cragun For This Post:
|
|
7 More Discussions You Might Find Interesting
1. Programming
question: for the below program
i just printed the value for pid, child pid and parent pid
why does it give me 6 values? i assume ppid is 28086
but can't figure out why there are 5 values printed instead of just two!
can someone comment on that!
#include<stdio.h>
#define DIM 8
int... (3 Replies)
Discussion started by: a25khan
3 Replies
2. What is on Your Mind?
Okay, I don't know how this is funny, but it is. I found this while searching for Linux (please don't ask). :o (0 Replies)
Discussion started by: gnerd
0 Replies
3. UNIX for Dummies Questions & Answers
1. If I use an software application(which connects to the database in the server) in my local pc, how many PID should be registered? Would there be PID for the session and another PID for socket connection?
2. I noticed (through netstat) that when I logged in using the my software application,... (1 Reply)
Discussion started by: pcx26
1 Replies
4. Post Here to Contact Site Administrators and Moderators
This a great service! I'm just curious how the people who are paying for the server, domain name, etc. are paying their bills. It doesn't look like this site generates any income through ads... why not try putting google's adwords on the site? Seems like it would be free money. (1 Reply)
Discussion started by: scottish
1 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I need to get the pid of a process and have to store the pid in a variable and i want to use this value(pid) of the variable for some process. Please can anyone tell me how to get the pid of a process and store it in a variable. please help me on this.
Thanks in advance,
Amudha (7 Replies)
Discussion started by: samudha
7 Replies
6. UNIX for Advanced & Expert Users
Hi,
I am having trouble transferring files from a source UNIX machine to a
destination UNIX machine by hopping via 2 gateway machines.
The user used for the transfer has been setup/authorized so no password is
required to login. Summerized:
source to gateway1 to gateway2 to destination ... (2 Replies)
Discussion started by: Solarius
2 Replies
7. Solaris
Hi gurus,
I can not seem to be able to run format completely on my t2000 (Sol 10), it just hangs there and I cannot kill it.
I know that it is probably trapped in the kernel somewhere (far from the user space) and this is the reason i can not kill it but I would like to determine how to know... (2 Replies)
Discussion started by: plmachiavel
2 Replies
LEARN ABOUT MOJAVE
kill
KILL(1) BSD General Commands Manual KILL(1) NAME
kill -- terminate or signal a process SYNOPSIS
kill [-s signal_name] pid ... kill -l [exit_status] kill -signal_name pid ... kill -signal_number pid ... DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operands. Only the super-user may send signals to other users' processes. The options are as follows: -s signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -l [exit_status] If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status. -signal_name A symbolic signal name specifying the signal to be sent instead of the default TERM. -signal_number A non-negative decimal integer, specifying the signal to be sent instead of the default TERM. The following PIDs have special meanings: -1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user. Some of the more commonly used signals: 1 HUP (hang up) 2 INT (interrupt) 3 QUIT (quit) 6 ABRT (abort) 9 KILL (non-catchable, non-ignorable kill) 14 ALRM (alarm clock) 15 TERM (software termination signal) Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page. EXIT STATUS
The kill utility exits 0 on success, and >0 if an error occurs. EXAMPLES
Terminate the processes with PIDs 142 and 157: kill 142 157 Send the hangup signal (SIGHUP) to the process with PID 507: kill -s HUP 507 SEE ALSO
builtin(1), csh(1), killall(1), ps(1), sh(1), kill(2), sigaction(2) STANDARDS
The kill utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible. HISTORY
A kill command appeared in Version 3 AT&T UNIX. BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided. BSD
April 28, 1995 BSD