From owner-freebsd-ports@freebsd.org  Thu Sep  6 16:41:09 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52173FCC780
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Thu,  6 Sep 2018 16:41:09 +0000 (UTC)
 (envelope-from leeb@ratnaling.org)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com
 [IPv6:2607:f8b0:4001:c0b::233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E46E87F4E0
 for <freebsd-ports@freebsd.org>; Thu,  6 Sep 2018 16:41:08 +0000 (UTC)
 (envelope-from leeb@ratnaling.org)
Received: by mail-it0-x233.google.com with SMTP id h3-v6so15945330ita.2
 for <freebsd-ports@freebsd.org>; Thu, 06 Sep 2018 09:41:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=ratnaling-org.20150623.gappssmtp.com; s=20150623;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
 bh=azwJyYTlQxmUoW/onK7yRdpWCRUgxgza35V5BSnNUnA=;
 b=SgiGHQb4mHEhtHCy629YBZi+WoY8EOFN7KX1SvbHvgt1Wgn4Fi+4ckIgp3losJpH/+
 OKQby6WQ04ySbbV5mL/t4sxTHD7lIdgW5FV7lSwSCwzXu6NI7z2lC4F8c3gGXWBhJrBK
 WL1MmxVQkcciMs4KYO5j9ekIbWBGG/YHYfcacDGU9l13LFkNLmnx0raHuYLY+10ODjc+
 w0oozwv0q+DGyyhzQpmiK6mNg85xWHymY5IOnnaTt3wt5z0HOqW3Ic3UYlUyK61YHe8x
 ExxyX1IQZj05NQWacPsBKLJAjVtC0nQOtgNh0LUv3h4SjmEjV/n7Vw0uCTNni/KIvBtk
 rGHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:in-reply-to:references:from:date
 :message-id:subject:to;
 bh=azwJyYTlQxmUoW/onK7yRdpWCRUgxgza35V5BSnNUnA=;
 b=UFTfAPrVpq4tcFASrdVdHkZN8DgGwurZG7ome+SxE1yv+cstXYviL6dxqNJtBCS28O
 rLAwxs4svLkYdZOZ/xOe3pI/6QOaGY2FIfSaEDrJGgqsNnqTNfdj0RjhQ20cOJI2zOmi
 eZ/eic++WP2fP4ch8GN1tTlm9hnvF/J2wF9s+y0VMr1x2Dt/0vbH8m+wbJXyIMgY03Dw
 iNkc1EaFFhSYDMWol98767aVekBN2D8clv1ZrE9gmlNxDznvq5BnkqRJv0QCk6HRlZV2
 S4+GYkYnFLnNDhLyhNabp5viWGDoT7XFTdOOZ86mNspqOM9g0CpEcnyqmBVwzIcHWRcy
 T+kg==
X-Gm-Message-State: APzg51AE3b2vUuq90Ywehq26wv+EVckd9NZ/8UQm72uxFTJ1RQuOVZve
 4id2MvPy0ReQn57PnjeaCAtc13WEGo/lMSRuXim5Cclgw5I=
X-Google-Smtp-Source: ANB0VdYk8n007hqMjrAhwH9khdTcvUr73el3HGsrmsJHjkAF5BZ9FcVtm0wZ1HLi/qb2tNXjpxHAIDELGPSbImnfDmg=
X-Received: by 2002:a6b:f609:: with SMTP id
 n9-v6mr2775314ioh.259.1536252067744; 
 Thu, 06 Sep 2018 09:41:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:d14f:0:0:0:0:0 with HTTP;
 Thu, 6 Sep 2018 09:41:07 -0700 (PDT)
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>
From: Lee Brown <leeb@ratnaling.org>
Date: Thu, 6 Sep 2018 09:41:07 -0700
Message-ID: <CAFPNf5-FWV3uEfPHu0wjJzEYYTmu05z-QvVPVkDApoqxh=4nKA@mail.gmail.com>
Subject: Re: Wrong log and archive permissions in Nagios
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.27
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2018 16:41:09 -0000

On Thu, Sep 6, 2018 at 4:43 AM, Per olof Ljungmark <peo@nethead.se> wrote:

> Hi,
>
> On 9/6/18 12:42 PM, Andrea Venturoli wrote:
> > Hello.
> >
> > I run several instances of Nagios and they all share a problem: reports,
> > alert histories, notifications, etc... cannot be viewed due to
> > permission problems.
> > In fact all the files are owned by nagios and access is denied to user
> > www. Of course I can chown/chmod them, but it's not a permanent solution
> > as rotation or new file creation will bring the problem back.
> >
> > 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? 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 run  nagios4-4.4.4.1,1 it works fine, as you describe.  Self built with
poudriere.