From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/pnp4nagios/
Date: Sat, 4 Nov 2017 23:40:20 +0000 (UTC) [thread overview]
Message-ID: <1509838643.8e44298fd864c4a30a38f47522679a20a317732c.mjo@gentoo> (raw)
commit: 8e44298fd864c4a30a38f47522679a20a317732c
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 3 00:27:45 2017 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Sat Nov 4 23:37:23 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8e44298f
net-analyzer/pnp4nagios: tighten permissions on process_perfdata.cfg.
With USE=apache2, we used to set the group of process_perfdata.cfg to
"apache2", but that appears unnecessary. This revision doesn't do it.
Package-Manager: Portage-2.3.8, Repoman-2.3.3
.../{pnp4nagios-0.6.26-r6.ebuild => pnp4nagios-0.6.26-r7.ebuild} | 5 -----
1 file changed, 5 deletions(-)
diff --git a/net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r6.ebuild b/net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r7.ebuild
similarity index 94%
rename from net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r6.ebuild
rename to net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r7.ebuild
index 9642d1e6479..4057b829d9e 100644
--- a/net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r6.ebuild
+++ b/net-analyzer/pnp4nagios/pnp4nagios-0.6.26-r7.ebuild
@@ -70,11 +70,6 @@ src_install() {
if use apache2 ; then
insinto /etc/apache2/modules.d
newins "${FILESDIR}"/98_pnp4nagios-2.4.conf 98_pnp4nagios.conf
-
- # This one file isn't world-readable, but it should be group-
- # readable. Give it to the "apache" group to let the web
- # server read it.
- fowners :apache /etc/pnp/process_perfdata.cfg
fi
# The nagios or icinga user needs to write performance data to the
next reply other threads:[~2017-11-04 23:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:40 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-04 13:35 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/pnp4nagios/ Sam James
2023-11-04 12:25 Sam James
2023-11-04 10:49 Sam James
2023-09-23 15:07 Michael Orlitzky
2023-09-23 15:07 Michael Orlitzky
2022-12-23 13:48 Arthur Zamarin
2022-12-23 13:48 Arthur Zamarin
2022-12-23 12:17 Sam James
2022-08-30 10:06 Michael Orlitzky
2022-08-29 12:38 Jakov Smolić
2022-08-12 14:27 Sam James
2022-08-03 16:12 Arthur Zamarin
2020-03-17 7:32 Matthew Thode
2020-02-17 23:37 Matthew Thode
2018-06-19 22:24 Michael Orlitzky
2018-03-19 23:24 Sergei Trofimovich
2018-03-19 22:39 Sergei Trofimovich
2017-11-29 18:52 Thomas Deutschmann
2017-11-29 13:38 Agostino Sarubbo
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2017-11-04 23:40 Michael Orlitzky
2016-11-30 23:44 Patrice Clement
2016-03-15 11:08 Agostino Sarubbo
2016-02-06 23:31 Matt Thode
2016-02-01 14:45 Matt Thode
2015-12-16 22:11 Matt Thode
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1509838643.8e44298fd864c4a30a38f47522679a20a317732c.mjo@gentoo \
--to=mjo@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox