Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Sep 2018 18:34:55 +0200
From:      Andrea Venturoli <ml@netfence.it>
To:        Per olof Ljungmark <peo@nethead.se>, freebsd-ports@freebsd.org
Subject:   Re: Wrong log and archive permissions in Nagios
Message-ID:  <30d5cc32-a7a1-6849-3a17-996c4f5acd84@netfence.it>
In-Reply-To: <7ea82acf-e403-96ca-ce4a-311229149895@nethead.se>
References:  <dd8273ef-6303-fd7d-9a69-21a6087bcbe0@netfence.it> <7ea82acf-e403-96ca-ce4a-311229149895@nethead.se>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9/6/18 1:43 PM, Per olof Ljungmark wrote:

>> I see this was discussed here:
>> https://github.com/NagiosEnterprises/nagioscore/issues/303
>>
>> and I understand correctly this is supposed to be fixed upstream.
>> Is it a problem specific to our FreeBSD port?
> 
> This is interesting, which version are you on?

nagios4-4.4.1,1



> I am on 3.5.1_11 and do
> not have this problem because nagios.log in /var/spool/nagios/ is owned
> by nagios:nagios *and* readable by (o)thers, ie. 644.

I remember this worked in the past, but I did not take note if this 
broke when I update from version 3 to 4.



  bye & Thanks
	av.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30d5cc32-a7a1-6849-3a17-996c4f5acd84>