avc: denied { read } for pid=1482 exe=/sbin/nash name=control dev=dm-0
ino=735844 scontext=system_u:system_r:initrc_t
tcontext=system_u:object_r:lvm_control_t tclass=chr_file
Booting SE Linux with strict policy gives the above audit message.
Why does nash need read access to this device node? nash will re-create it if
necessary, but that doesn't require read access.
What access does reading it really give anyway?
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
