Description of problem: ======================= The man page for "ps" does not indicate what a lowercase "T" means (probably "traced by another user") Man page has to be updated. Version-Release number of selected component (if applicable): ============================================================= procps-3.2.8-28.20110302git.fc17.x86_64
Hello David. Is it a switch or a column 'value' you're talking about? Please, be more specific. Thank you. Regards, Jaromir.
Hi Jaromir, You are right, that's pretty unclear. It's the value (status) displayed. For example: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 2 0.0 0.0 0 0 ? S 08:51 0:00 [kthreadd] root 3 0.0 0.0 0 0 ? S 08:51 0:00 \_ [kso root 5 0.0 0.0 0 0 ? S< 08:51 0:00 \_ [kwo root 7 0.0 0.0 0 0 ? S< 08:51 0:00 \_ [kwo root 8 0.0 0.0 0 0 ? S 08:51 0:04 \_ [mig .... hobbes 1414 0.0 0.4 425468 17452 ? t 08:52 0:06 /usr/bin/klipper Here "klipper" is being traced by root. The manual just says: ---- T stopped, either by a job control signal or because it is being traced ----
Ok. Now it's clear. It seems the same applies to procps-ng. Gonna check and fix the manpage. Thank you for the report. Regards, Jaromir.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It seems the kernel documentation doesn't cover the lowercase 't': https://www.kernel.org/doc/Documentation/filesystems/proc.txt ... as you can see, the docs list just the "RSDZT" letters and the procps code additionally adds a combination of "<NLsl+".
The documentation contains teh following .... ------------------------------- State state (R is running, S is sleeping, D is sleeping in an uninterruptible wait, Z is zombie, T is traced or stopped) ------------------------------- Changing the component to kernel to get their statement and/or a documentation fix.
/* * The task state array is a strange "bitmap" of * reasons to sleep. Thus "running" is zero, and * you can test for combinations of others with * simple bit tests. */ static const char * const task_state_array[] = { "R (running)", /* 0 */ "S (sleeping)", /* 1 */ "D (disk sleep)", /* 2 */ "T (stopped)", /* 4 */ "t (tracing stop)", /* 8 */ "Z (zombie)", /* 16 */ "X (dead)", /* 32 */ }; is the array present in fs/proc/array.c. What 'tracing stop' means, I have no idea. Oleg would likely know though.
Looking at include/linux/sched.h it seems 'T' is STOPPED and 't' is TRACED. Why it's called 'tracing stop'... no idea.
(In reply to Josh Boyer from comment #10) > > Looking at include/linux/sched.h it seems 'T' is STOPPED and 't' is TRACED. Yes, exactly. So "t" means stopped by debugger. > Why it's called 'tracing stop'... no idea. ... and too late to change ;)
Thanks guys. I'll document it in the procps-ng manuals. Please, do the same in case of the kernel documentation.
Just a short clarification ... the following is the current description of the capital T in the procps-ng manual. T - stopped, either by a job control signal or because it is being traced ... so, if I understand correctly, it needs to be split to the following two descriptions T - stopped by a job control signal t - stopped by debugger during the tracing Is that correct?
(In reply to Jaromír Cápík from comment #13) > > ... so, if I understand correctly, it needs to be split to the following two > descriptions > > T - stopped by a job control signal Yes. SIGCONT can wake it up, other signals can't (except SIGKILL). > t - stopped by debugger during the tracing > > Is that correct? Yes. But just in case, the task still can be stopped by jctl, but since it runs under debugger it will actually stop in TASK_TRACED and thus it will be reported as "t" in /proc. SIGCONT won't work. SIGKILL should wake it up (and kill ;) in both cases.
(In reply to Oleg Nesterov from comment #14) > > Yes. But just in case, the task still can be stopped by jctl, but > since it runs under debugger it will actually stop in TASK_TRACED > and thus it will be reported as "t" in /proc. To clarify, this is true starting from (approx) v3.0 kernel. Previously a traced task could stop in TASK_STOPPED, although this state was not "stable", it could be silently turned into TASK_TRACED.
I think the description doesn't need to be so detailed in case of the procps-ng manual. But feel free to document that behaviour in the kernel docs.
procps-ng-3.3.8-13.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/procps-ng-3.3.8-13.fc19
procps-ng-3.3.8-17.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/procps-ng-3.3.8-17.fc20
procps-ng-3.3.8-17.fc20 works
procps-ng-3.3.8-17.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.14.4-100.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
procps-ng-3.3.8-13.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.