On 7/28/06, Ed Kim <ed.kim@xxxxxxxxxxx> wrote:
Patrick Doyle wrote: > I thought about that after I sent my email... Gee, probably won't help > you at all, but the button had been pressed and the email sent... > > Anyway, > Once before I have seen a file that root couldn't delete. It was on a > badly hosed disk that had suffered a fatal data destroying fsck. I > was about to contact the maintainers of ext3 and say to them "Do you > want to see a disk image on which root cannot delete a file?", when I > thought to check the extended attributes (via "lsattr") -- sure > enough, the file system had been corrupted enough that some attribute > had been set that inhibited even root from removing the file (perhaps > it was flagged as "immutable" -- I don't recall now). > > The other thought that comes to mind is SELinux, about which I know > absolutely nothing. > > --wpd > Are there any relevant messages in /var/log/messages ? if it is selinux, you can try the command 'setenforce 0' to temporarily disable it and rerun the rpm command. -- Ed Kim, RHCE http://www.rhatbox.com -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
I tried to look in /var/log/messages but could not find something related permission, more of the selinux messages were in "activated ... device hda... autofs etc. I tried "setenforce 0" and run the rpm, it works. I had put back to "setenforce 1". Now I need to know which selinux setting I need to tweak so that this wont happen again. Thanks
