We are running samba3 on a RHEL SELinux server and are constantly receiving (approximately a new one per every 6 to 12 seconds) invalid context message in /var/log/messages. This message disappears when setting SELinux to permissive. At no time is there an AVC entry being written to the audit.log file. I tried increasing the debug level for samba, but that didn't generate any additional information in the log file regarding this invalid context issue. The PID being reported with each log entry is ever changing and it does not run long enough to catch. Red Hat Enterprise Linux Server release 5.6 (Tikanga) Samba version: Version 3.5.4-0.70.el5_6.1 (installed samba3x rpm using yum)
smbd[****]: file_contexts: invalid context system_u:object_r:samba_var_t:s0 The only entries I found with this samba_var_t set under /var were: system_u:object_r:samba_var_t ./spool/samba system_u:object_r:samba_var_t ./lib/samba system_u:object_r:samba_var_t ./lib/samba/browse.dat system_u:object_r:samba_var_t ./lib/samba/private I verified that all the required Boolean settings were in place and functioning as expected. Does anyone have any suggestions on how to resolve this issue? Or even how to actually force additional information be provided in order to track down and find a resolution? Thanks in advance, Scott -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
