From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 732de6575124e6fa091d61c26142b2a568d3591a
Date: Sat, 12 May 2018 21:06:42 +0100 [thread overview]
Message-ID: <20180512200642.933301081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 732de6575124e6fa091d61c26142b2a568d3591a (commit)
from 8080197b129b82c93dffc77b970aa7028c0ba4a0 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 732de6575124e6fa091d61c26142b2a568d3591a
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date: Sat May 12 14:57:37 2018 +0200
Add NRPE initscript to rootfile
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/packages/nagios_nrpe | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/packages/nagios_nrpe b/config/rootfiles/packages/nagios_nrpe
index 89f74c92d..1da6c3baf 100644
--- a/config/rootfiles/packages/nagios_nrpe
+++ b/config/rootfiles/packages/nagios_nrpe
@@ -1,5 +1,6 @@
etc/nagios
etc/nagios/nrpe.cfg
+etc/rc.d/init.d/nrpe
#root/.rnd
#usr/bin/nrpe-uninstall
usr/bin/nrpe
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-05-12 20:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180512200642.933301081DF2@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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