Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you are running with selinux in enforcing mode, it will also give that type of listing if you don't have a policy setting to allow you to read the file. Since you don't want the directory, try "rm -rf xxx/yyy/zzz/bin" instead of rmdir.
Access permissions are visible at all times, ownership is only left untranslated if the Id doesn't exist (and since SELinux operates on top of DAC this would be an odd policy rule AFAIK). So I second running fsck.
If you can't detect file system corruption I'd also try rkhunter. The only time I've seen a rootkit on one of my machines I detected a few files like this one. I couldn't delete them and fsck didn't report anything. Finally I had to use debugfs to remove them. This was on a grsecurity hardened machine by the way.
Last edited by i92guboj; 08-10-2009 at 08:17 PM.
Reason: it wasn't selinux, but grsecurity, corrected
OK, odd it may be, but I've seen it many times first hand. Running fsck won't hurt in any event. Just make sure you are running it on an unmounted partition if you are in a "fixing" mode.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.