Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 247195 - samba logfile warning
samba logfile warning
Product: Fedora
Classification: Fedora
Component: selinux-policy-targeted (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2007-07-05 17:20 EDT by Dave Jones
Modified: 2015-01-04 17:29 EST (History)
1 user (show)

See Also:
Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-22 10:09:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Jones 2007-07-05 17:20:47 EDT
SELinux is preventing samba (/usr/sbin/smbd) "append" to

SELinux denied samba access to If you want to share this
directory with samba it has to have a file context label of samba_share_t. If
you did not intend to use as a samba repository it could
indicate either a bug or it could signal a intrusion attempt.

This is odd.
I'm not trying to share /var/log/samba/ , so afaics, it's
correctly labelled already..

(17:16:22:root@gelk:samba)# ll -Z 
-rw-r--r--  root root system_u:object_r:samba_log_t

Hmm, there is some discrepancy though between this and other files in that dir..

-rw-r--r--  root root system_u:object_r:samba_log_t
-rw-r--r--  root root user_u:object_r:samba_log_t

Not sure why samba keeps trying to bother with this file at all, that host
hasn't been switched on for about a month.
Comment 1 Daniel Walsh 2007-07-06 10:47:20 EDT
What policy are you seeing this with?

It should be fixed by the latest policy?  selinux-policy-2.6.4-26
Comment 2 Dave Jones 2007-07-15 17:33:16 EDT
haven't seen it happen since updating to that version, but will keep an eye open
for it.
Comment 3 Daniel Walsh 2007-08-22 10:09:23 EDT
Closing as fixes are in the current release

Note You need to log in before you can comment on or make changes to this bug.