Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

process with no cmd are shown with no name #2315

Closed
rade opened this issue Mar 9, 2017 · 0 comments
Closed

process with no cmd are shown with no name #2315

rade opened this issue Mar 9, 2017 · 0 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@rade
Copy link
Member

rade commented Mar 9, 2017

Launch scope on your machine (or look at pretty much any instance in Weave Cloud), bring up a host details panel, and look at the list of processes. Observe that many process names are blank.

screenshot_2017-03-09_13-19-19

Contrast with ps:

root     27901  0.0  0.0      0     0 ?        S    13:09   0:00 [kworker/2:2]

That's probably because

# cat /proc/27901/cmdline 
# cat /proc/27901/comm
kworker/2:2
@rade rade added the bug Broken end user or developer functionality; not working as the developers intended it label Mar 9, 2017
@2opremio 2opremio added this to the 1.3 milestone Mar 9, 2017
@rade rade self-assigned this Mar 9, 2017
rade added a commit that referenced this issue Mar 9, 2017
when proc/<pid>/cmdline is empty, which is the case for some system
and defunct processes.

Fixes #2315
@rade rade closed this as completed in #2316 Mar 9, 2017
rade added a commit that referenced this issue Mar 9, 2017
fall back to /proc/<pid>/comm for process name

Fixes #2315
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

2 participants