Debugging recent problem here I pbserved following:
stracing devfsd for the first time using simple
strace -p 69
ends spitting out a screenfull of lines las one being output to stderr
about broken pipe.
Stracing the same devfsd the second time puts it into endless loop
scanning /dev recursively and running REGISTER actions; if strace is
killed immediately, devfsd calms down after 18s CPU time! (as reported
by ps). I guess it is some bad interaction - devfsd does /dev rescan
*every* time it receives an event from devfs and stracing process
interrupts read.
Is this rescan every time really necessary? Do I correctly understand it
tries to compensate for missing events? But then it could check for
overrun_count? Doing full rescan is very inefficient, at least here
where we apply permissions every time.
-andrej
|