dnf install fatrace "fatrace" as root
why *all the time*
konsole(25441): RCO /etc/passwd konsole(25441): O /etc/passwd konsole(25441): R /etc/passwd konsole(25441): CO /etc/passwd konsole(25441): R /etc/passwd konsole(25441): C /etc/passwd konsole(25441): O /etc/passwd konsole(25441): R /etc/passwd konsole(25441): C /etc/passwd konsole(25441): O /etc/passwd konsole(25441): R /etc/passwd konsole(25441): C /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): O /etc/passwd konsole(25441): R /etc/passwd konsole(25441): C /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): C /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): O /etc/passwd konsole(25441): RC /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): C /etc/passwd konsole(25441): O /etc/passwd konsole(25441): RCO /etc/passwd konsole(25441): C /etc/passwd konsole(25441): O /etc/passwd konsole(25441): R /etc/passwd konsole(25441): C /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): C /etc/passwd konsole(25441): O /etc/passwd konsole(25441): RC /etc/passwd konsole(25441): RO /etc/passwd konsole(25441): C /etc/passwd
Am 26.04.2016 um 16:09 schrieb Luigi Toscano:
On Tuesday 26 of April 2016 16:05:59 Reindl Harald wrote:
dnf install fatrace "fatrace" as root
why *all the time*
konsole(25441): RCO /etc/passwd
Rough guess: from the current Konsole profile, "Tabs", "Tab Titles", what is the format?
that's hardly a reason access multiple times per second for every tab
Am 26.04.2016 um 16:21 schrieb Reindl Harald:
Am 26.04.2016 um 16:09 schrieb Luigi Toscano:
On Tuesday 26 of April 2016 16:05:59 Reindl Harald wrote:
dnf install fatrace "fatrace" as root
why *all the time*
konsole(25441): RCO /etc/passwd
Rough guess: from the current Konsole profile, "Tabs", "Tab Titles", what is the format?
that's hardly a reason access multiple times per second for every tab
ok, it's probably the reason but a bad style
On Tue, 2016-04-26 at 16:09 +0200, Luigi Toscano wrote:
On Tuesday 26 of April 2016 16:05:59 Reindl Harald wrote:
dnf install fatrace "fatrace" as root
why *all the time*
konsole(25441): RCO /etc/passwd
Rough guess: from the current Konsole profile, "Tabs", "Tab Titles", what is the format?
Just for interest, I ran fatrace for 60 seconds on my system and got the attached output (filtered for references to /etc/passwd). So it's not just konsole.
poc
On Tuesday, April 26, 2016 04:09:28 PM Luigi Toscano wrote:
On Tuesday 26 of April 2016 16:05:59 Reindl Harald wrote:
dnf install fatrace "fatrace" as root
why *all the time*
konsole(25441): RCO /etc/passwd
Rough guess: from the current Konsole profile, "Tabs", "Tab Titles", what is the format?
Doesn't appear to be. I did some testing of my own and changed my shell to '/bin/sh' as well as unsetting all of the tab variables (so that it just shows "Shell")
None of that had any effect on the amount or polling resolution of /etc/passwd. In fact, I could correlate no profile settings to why it's polling /etc/passwd so frequently.
I can confirm that this is a call to NSS though, because if you change 'passwd: files sss' to 'passwd: sss' it ceases that behavior. (though don't do that unless you have a root tty already open and ready to edit it back again)
These are the files it's opening every second:
open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 14 open("/etc/passwd", O_RDONLY|O_CLOEXEC) = 14 open("/proc/26191/stat", O_RDONLY|O_CLOEXEC) = 14 open("/proc/26191/cmdline", O_RDONLY|O_CLOEXEC) = 12 open("/proc/26191/status", O_RDONLY|O_CLOEXEC) = 12
26191 was the child bash shell
---------
Others have noticed the "problem" as well:
KDE Bug: https://bugs.kde.org/show_bug.cgi?id=325442 unix.SE Post: https://unix.stackexchange.com/questions/125500/why-is-konsole-reading-etc-p...
The consensus is that it's benign, which is like a given.
What isn't properly addressed is why it needs second resolution when it's just sitting there idling.
What's likely necessary is a look at the source to determine what is polling /proc/$CHILD_PID/{stat,cmdline,status} and you'll probably find the answer there.