Sponsored Content
Operating Systems OS X (Apple) The Great Hopping Unkillable PID Post 302909010 by aaronbsdf on Sunday 13th of July 2014 01:57:09 PM
Old 07-13-2014
The Great Hopping Unkillable PID

Hi all,

VLC goes all SWOD on me today, so naturally I try to force quit the process.

Nothing.

Drop into Terminal and run ps ax | grep vlc,
noting that kill has no effect, nor killall. The PID is hopping up!
W
T
F?

MADDENING! Killall was made for this right? Killall says no such process or some bs. Computers effing suck sometimes.

Does anyone know why a PID is hopping up by increments of 3, and occasionally 3? It isn't a virus but it sure acts like one, whatever this cause. But most impotantly:
How can I kill an unkillable process? Is there any other command I can use? Maybe NUKEEFFINGPS or something? Makes me wanna throw my MBP out the freekin window it does.

Last edited by aaronbsdf; 07-13-2014 at 03:06 PM..
 

7 More Discussions You Might Find Interesting

1. Programming

printing ppid,child pid,pid

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?

Great deal!

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

Session PID & socket connection pid

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

Great service -- why?

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

Need to get pid of a process and have to store the pid in a variable

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

ssh - transfers with gateway hopping

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

unkillable format process

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
KILLALL(1)							   User Commands							KILLALL(1)

NAME
killall - kill processes by name SYNOPSIS
killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con- text] [-s,--signal signal] [--] name ... killall -l killall -V,--version DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1). If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name. killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise. A killall process never kills itself (but may kill other killall processes). OPTIONS
-e, --exact Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e. it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e, -g, --process-group Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong- ing to the same process group were found. -i, --interactive Interactively ask for confirmation before killing. -l, --list List all known signal names. -q, --quiet Do not complain if no processes were killed. -v, --verbose Report if the signal was successfully sent. -V, --version Display version information. -w, --wait Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie state. -S (Flask only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument. Must precede other arguments on command line. -c (Flask only) Specify security context: kill only processes with given security context. Mutually exclusive with -s. Must precede other arguments on the command line. FILES
/proc location of the proc file system KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way. Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user. killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans. AUTHORS
Werner Almesberger <Werner.Almesberger@epfl.ch> wrote the original version of psmisc. Since version 20 Craig Small <csmall@small.drop- bear.id.au> can be blamed. SEE ALSO
kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2) Linux March 25, 2001 KILLALL(1)
All times are GMT -4. The time now is 01:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy