smb can't access its own logfiles?

[dragoran]

Paul Howarth wrote:
> dragoran wrote:
>> Paul Howarth wrote:
>>> On Sun, 2006-07-30 at 19:04 +0200, dragoran wrote:
>>>  
>>>> I got this erros:
>>>> audit(1154259027.504:4): avc:  denied  { create } for  pid=2610 
>>>> comm="smbd" name="cores" scontext=system_u:system_r:smbd_t:s0 
>>>> tcontext=system_u:object_r:samba_log_t:s0 tclass=dir
>>>> audit(1154259027.996:5): avc:  denied  { create } for  pid=2613 
>>>> comm="nmbd" name="cores" scontext=system_u:system_r:nmbd_t:s0 
>>>> tcontext=system_u:object_r:samba_log_t:s0 tclass=dir
>>>> on a FC5 system running
>>>> selinux-policy-targeted-2.3.2-1.fc5 and samba-3.0.23a-1.fc5.1
>>>> is this a known bug/regression or should I fill a bug report?
>>>>     
>>>
>>> I saw this too.
>>>
>>> Samba wants to create the directories:
>>>
>>> /var/log/samba/cores/smbd
>>> /var/log/samba/cores/nmbd
>>>
>>> and set their modes to 0700. It dumps core into these directories if it
>>> detects an internal error, as described here:
>>>
>>> http://samba.org/samba/docs/man/Samba-HOWTO-Collection/bugreport.html
>>>
>>>   
>> so in short this is a policy bug right?
>
> Yes, I would say so.
>
ok, bug reported
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200914
> Paul.
>
>