Date: Tue, 30 Oct 2018 12:07:40 +0000 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 Message-ID: <bug-232813-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232813-7788>