Hello, I'm planning to update syslog-ng to the latest beta release (3.3 final should be here real soon now). I checked the current syslog-ng in factory and ran into an interesting problem: linux-1wrf:/etc/apparmor.d # rcsyslog start Starting syslog servicesError opening file for reading; filename='/proc/kmsg', error='Operation not permitted (1)' Error initializing source driver; source='src', id='src#1' Error initializing message pipeline; startproc: exit status of parent of /sbin/syslog-ng: 2 failed linux-1wrf:/etc/apparmor.d # grep kmsg sbin.syslog-ng @{PROC}/kmsg r, It works fine when I disable AppArmor. Any hints why I get "Operation not permitted", when access to the file is actually allowed? Bye, CzP (from syslog-ng upstream) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org