The Day “/Proc” Died

Re:The Day “/Proc” Died by wahern on Tuesday July 02, 2019 @03:44PM (#20338725)

Wow, that's almost exactly the same problem I encountered in Linux last week, where simply reading /proc/$pid/cmdline would block the process attempting to read the process info. It appears to have been related to this issue:

  https://lkml.org/lkml/2018/2/20/576

And much like the Solaris issue, as best I could tell the original processes (this occurred multiple times on two different nodes) would seem to be blocked either in the filesystem or memory management layers flushing pages.

[ Parent | on HN ]

Re:The Day “/Proc” Died by majewsky on Wednesday July 03, 2019 @04:59AM (#20342747)

Please don't put things that are not code in codeblocks. In this case, it makes the link unclickable for no good reason. Working link: https://lkml.org/lkml/2018/2/20/576

[ Parent | on HN ]

Re:The Day “/Proc” Died by souprock on Tuesday July 02, 2019 @05:17PM (#20339490)

This is part of why I resisted requests to make the Linux ps command sort processes by default. Half a process listing is a useful hint.

It also saves memory, which is great on the insane 10240-core boxes.

[ Parent | on HN ]