From owner-freebsd-ports-bugs@freebsd.org Tue Oct 30 12:07:43 2018 Return-Path: Delivered-To: freebsd-ports-bugs@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 5F5A310E1F05 for ; Tue, 30 Oct 2018 12:07:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D455E80E47 for ; Tue, 30 Oct 2018 12:07:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9957F10E1F04; Tue, 30 Oct 2018 12:07:42 +0000 (UTC) Delivered-To: ports-bugs@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 776FB10E1F03 for ; Tue, 30 Oct 2018 12:07:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0237F80E46 for ; Tue, 30 Oct 2018 12:07:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E16BB1424C for ; Tue, 30 Oct 2018 12:07:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9UC7eq5002747 for ; Tue, 30 Oct 2018 12:07:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9UC7eYF002746 for ports-bugs@FreeBSD.org; Tue, 30 Oct 2018 12:07:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 232813] [PATCH] net-mgmt/prometheus2: Remove syslog and newsyslog config files from port Date: Tue, 30 Oct 2018 12:07:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: dor.bsd@xm0.uk X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2018 12:07:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232813 Bug ID: 232813 Summary: [PATCH] net-mgmt/prometheus2: Remove syslog and newsyslog config files from port Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: dor.bsd@xm0.uk Created attachment 198771 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D198771&action= =3Dedit net-mgmt/prometheus2: Remove syslog config files This patch removes the syslog and newsyslog config files for now for a few reasons. - I'd originally intended them to be examples that a user could take and = use if they wanted to redirect Prometheus syslog entries to their own log files, however, they were turned into @sample entries during commit. - Without a reload of syslogd, simply placing the config files will do nothing and no instructions were included in pkg-message saying that the us= er should reload syslogd. - I am currently unsure if the package should be changing the users syslog config (although, after the @sample change, they did have to request it via= the SYSLOG option) - If they do request it, how to reload the syslog so that the config file= is used right away? Basically, I have far too many questions surrounding the feature now, so I'm removing it entirely until I have considered it further and spoken with some other porters on how they have handled syslog related things. I may add them back as examples again in the future with a suitable pkg-mes= sage about their existance. With this change, Prometheus will still sends its output to syslog, but wit= hout specific configuration the messages will be routed according to however the user has already configured their syslogd. This patch should also fix #232706, as there will be no syslog configs to be copying around anymore. --=20 You are receiving this mail because: You are the assignee for the bug.=