SE alert

[jd1008]

On 07/18/2015 08:07 PM, Ed Greshko wrote:
> On 07/19/15 09:55, jd1008 wrote:
>> Ooops, Sorry. Here it is:
>> $ sudo ls -l -i /* | grep 47972353
> OK....  How about
>
> sudo ls -l -i -R /root | grep 47972353
>
Well, now, this is interesting:

$ sudo ls -l -i -R /root | grep 47972353    <<<<< Produced no output
$ sudo ls -l -d -i -R /root | grep 47972353 <<<<<< adding the -d option, 
however:
47972353 dr-xr-x---. 9 root root 4096 Jul  2 14:03 /root
$

I really want to find which daemon/process is ultimately causing sh to try
to read /root and open it for reading?
Hopefully that might shed some light on why it is happening.