Disclaimer: Boring Video. NOT A TUTORIAL. I RAN INTO THIS PROBLEM RECENTLY AT WORK WHEN THE AWS SERVER I WAS ON FORCE CLOSED ECLIPSE ON ME BUT THE PROCESS WAS STILL RUNNING IN THE BACKGROUND.
PER Slava Ukraini!, please do not use the kill -9 command (as this abruptly kills the process). Please instead use regular kill command as it would safely kill the process. If regular kill command doesn’t work, then you might try kill -9 command!
The other day I was trying to close Eclipse application.
It crashed on me.. but I think it was still running.
After googling:
I came across the command pidof
i ran:
pidof eclipse
This returned one process that ran eclipse
The problem though.. is that if I try searching all of the processes that I’m the owner of:
ps -ef | grep eclipse
It will return multiple instances of eclipse processes running on linux.
In the video I try badly to show that you can look at the first number from the ps -ef command which returns the process id. The 2nd number to the right is the PARENT process id. So in theory.. if you only kill the parent process.. it will properly close all the children processes.
I used the following command to destroy the process:
kill -9 [PID]
That’s it.
So in some cases.. if you don’t know what the parent process id is.. you can maybe go ahead and delete all of the processes and through elimination it will finally close tha pplication you want.
If your workspace is being locked… that’s a different issue (you get an error that the workspace is already in use.)
one possible solution is to delete the .lock file in .metadata in your primary workspace directory.
[ad_2]
source
-
-
-
-
