[syslog-ng] Permissions Issues

[Evan Rempel]

I don't recall. I did both and it is working for me under Redhat 6.x

Evan.

On 4/16/19 8:53 AM, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
> In addition to upgrading to 3.19 or when using 3.18?
>
> Thanks,
> -Mark
>
> Mark Faine
> System Administrator
> SAIC/NICS
> 215 Wynn Dr. 5065
> Huntsville, AL 35805
> 256-961-1295 (Desk)
> 256-617-4861 (Work Cell)
>
>
> -----Original Message-----
> From: syslog-ng <syslog-ng-bounces at lists.balabit.hu> On Behalf Of Evan Rempel
> Sent: Tuesday, April 16, 2019 10:30 AM
> To: syslog-ng at lists.balabit.hu
> Subject: Re: [syslog-ng] Permissions Issues
>
> Oh, and I think I may have had to add the options of "--no-caps" to the launch of syslog-ng as well..
>
> Evan
>
> On 4/16/19 8:27 AM, Evan Rempel wrote:
>> I recall this bug in the 3.18 and it was fixed in the 3.19 release.
>>
>> On 4/16/19 8:23 AM, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
>>> syslog-ng 3.18.1
>>> RHEL 6.10
>>>
>>> Can someone please help me understand what I'm doing wrong?  I thought that when I set the following on a destination:
>>>
>>> create_dirs(yes);
>>> dir-owner(myuser);
>>> dir-group(myuser);
>>> group(myuser);
>>> owner(myuser);
>>> perm(0640);
>>>
>>> that files and directories would be created with those permissions, however, I'm seeing something strange.  It seems that syslog-ng still wants to create and write to files with root.root.  Also, and this is even more unexpected. If I change the permissions on the directories before starting syslog-ng, it fails to write to the directories that are not root.root.
>>>
>>> Am I missing something?
>>>
>>> Thanks,
>>> -Mark