On 07/18/2015 08:20 PM, Ed Greshko wrote:
On 07/19/15 10:15, jd1008 wrote:
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.
First make sure it is labeled correctly
[egreshko@meimei ~]$ ls -Zd /root
system_u:object_r:admin_home_t:s0 /root
$ ls -Zd /root
dr-xr-x---. root root system_u:object_r:admin_home_t:s0 /root/
$
On my output, there is a / after root
I am sure it is of no real consequence, but ..... there is always a but
!! :)
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
