Hi, It seems this event triggered by starting a virtual machine (virsh start fedora20). This command changes /dev/null permission to a wrong one... is this some configuration issue or should I fill a bug? Thx L: On 05/20/2014 08:13 PM, Michael Cronenworth wrote: > Pal, Laszlo (private) wrote: >> Recently I've discovered a strange thing... some rule/program or >> whatever changing the access rights of /dev/null to >> >> crw-------. 1 root root 1, 3 May 20 11:57 /dev/null >> >> and some of the part of Fedora does not like it:) >> >> After I change back to 666, everything is fine again, however after boot >> I have again the "wrong" permission >> >> is this a bug or feature?:) What can cause this? After google the >> problem, I can find some very old bug, so maybe it is back again >> >> Any idea? > > That is not normal. > > You could setup an auditctl rule to watch /dev/null for permission > changes. There is a manpage (and exhaustive support on Google) for > auditctl. > -- 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
