Hi,
Audacity not respond anymore on my computer...
That in not a problem for me now.. I only would kill his process.
Using the command ps ax I get the list of the processes and also their state (S, S<, SN, SNsl, Ssl, etc...).
I would ask what is the state of a process whose program program non respond anymore???
And also what (generally) the value of states of processes (S, S<, SN, SNsl, Ssl, etc...) means ??
Thank you
Angelo
On 07/18/16 14:32, Angelo Moreschini wrote:
Audacity not respond anymore on my computer...
That in not a problem for me now.. I only would kill his process.
Using the command ps ax I get the list of the processes and also their state (S, S<, SN, SNsl, Ssl, etc...).
I would ask what is the state of a process whose program program non respond anymore???
And also what (generally) the value of states of processes (S, S<, SN, SNsl, Ssl, etc...) means ??
Thank you
The are listed in "man ps".
Look for the section in the man page "PROCESS STATE CODES"
On 07/17/2016 11:32 PM, Angelo Moreschini wrote:
I would ask what is the state of a process whose program program non respond anymore???
It can be almost any state depending on why it's not responding. If it's stuck in an infinite loop, it will be "R". If it's deadlocked or just confused about it's input, it could be in "S". If there's a kernel problem or it's stuck in some I/O, it could be in "D" state. That's the worst one, because sometimes you can't even kill it with -9. But these are still just examples, there are many causes, so you really can't tell from the process state if it's not responding.
And also what (generally) the value of states of processes (S, S<, SN, SNsl, Ssl, etc...) means ??
"man ps". Look in the section called "PROCESS STATE CODES".
OK ! You are right I understand...
So i try another way ...
What can be the connection from a program and his process....
...What possibility I can have to know the name of a proces generate from a program ?
Thank you for answering me
On Mon, Jul 18, 2016 at 9:42 AM, Samuel Sieb samuel@sieb.net wrote:
On 07/17/2016 11:32 PM, Angelo Moreschini wrote:
I would ask what is the state of a process whose program program non respond anymore???
It can be almost any state depending on why it's not responding. If it's
stuck in an infinite loop, it will be "R". If it's deadlocked or just confused about it's input, it could be in "S". If there's a kernel problem or it's stuck in some I/O, it could be in "D" state. That's the worst one, because sometimes you can't even kill it with -9. But these are still just examples, there are many causes, so you really can't tell from the process state if it's not responding.
And also what (generally) the value of states of processes (S, S<, SN,
SNsl, Ssl, etc...) means ??
"man ps". Look in the section called "PROCESS STATE CODES".
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 07/18/2016 12:00 AM, Angelo Moreschini wrote:
What can be the connection from a program and his process....
...What possibility I can have to know the name of a proces generate from a program ?
There are a few ways. The simplest way is to do "ps auxw | grep -i <some part of the program name>". But sometimes the process name doesn't match the program name, so can "dnf search" the name to find the package name and then "rpm -ql <packagename" to find out the possible executable files that it might be running. If you know some file that the process has open, then you can do "lsof <path/to/file>".
Ok
thank you
On Mon, Jul 18, 2016 at 8:27 PM, Samuel Sieb samuel@sieb.net wrote:
On 07/18/2016 12:00 AM, Angelo Moreschini wrote:
What can be the connection from a program and his process....
...What possibility I can have to know the name of a proces generate from a program ?There are a few ways. The simplest way is to do "ps auxw | grep -i <some
part of the program name>". But sometimes the process name doesn't match the program name, so can "dnf search" the name to find the package name and then "rpm -ql <packagename" to find out the possible executable files that it might be running. If you know some file that the process has open, then you can do "lsof <path/to/file>".
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Mon, 2016-07-18 at 09:32 +0300, Angelo Moreschini wrote:
Hi,
Audacity not respond anymore on my computer...
That in not a problem for me now.. I only would kill his process.
Using the command ps ax I get the list of the processes and also their state (S, S<, SN, SNsl, Ssl, etc...).
I would ask what is the state of a process whose program program non respond anymore???
And also what (generally) the value of states of processes (S, S<, SN, SNsl, Ssl, etc...) means ??
It can sometimes be useful to trace the process to see what it's doing (or at least what system call it's hung in):
strace -p <pid>
For a process you don't own, you'll need to be root to do this.
poc
that require to know the pid... and this is what I am looking for... :-)
I understand that for my purpose I have to identify the process ... for this purpose we have to know something more about the program, the directory where is installed is already enough .
Thanks anyway, this talk has helped me
On Mon, Jul 18, 2016 at 11:49 AM, Patrick O'Callaghan <pocallaghan@gmail.com
wrote:
On Mon, 2016-07-18 at 09:32 +0300, Angelo Moreschini wrote:
Hi,
Audacity not respond anymore on my computer...
That in not a problem for me now.. I only would kill his process.
Using the command ps ax I get the list of the processes and also their state (S, S<, SN, SNsl, Ssl, etc...).
I would ask what is the state of a process whose program program non respond anymore???
And also what (generally) the value of states of processes (S, S<, SN, SNsl, Ssl, etc...) means ??
It can sometimes be useful to trace the process to see what it's doing (or at least what system call it's hung in):
strace -p <pid>
For a process you don't own, you'll need to be root to do this.
poc
users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Mon, 2016-07-18 at 13:19 +0300, Angelo Moreschini wrote:
that require to know the pid... and this is what I am looking for... :-)
Your original question did not make this clear. You asked about the meaning of various process states, so it's natural to assume you know what process you're looking at.
You might be able to identify the process if you know which files it uses. Check the output of lsof and fuser.
poc
Allegedly, on or about 18 July 2016, Angelo Moreschini sent:
Audacity not respond anymore on my computer...
That in not a problem for me now.. I only would kill his process.
You could try the brute-force and ignorance method:
killall audacity
Sometimes you have to do that more than once, it depends on how busy it is and how many things its running.
I wouldn't have thought it hard to find out that Audacity is run from the command "audacity". Yes, other programs can be very obscure, but not that one.
Using the "top" command can be a quick way to find out what program has gone doolally. If you've got something pegged at 100%, that may be it. Or you can sort the list by the first column, and see the most recently started applications at the top of the list. If you haven't started many other things, it's probably very close to the top, if not at the top (some processes get started by other things that are running, so you may have background tasks from other things still running get up to the top of the list).
Audacity can be stuck by other things, it depends on what you were doing. e.g. If you were exporting and encoding an audio file, it could be the encoder.
-
Angelo Moreschini -
Ed Greshko -
Patrick O'Callaghan -
Samuel Sieb -
Tim