From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] install initscript for NRPE
Date: Mon, 07 May 2018 11:32:00 +0100 [thread overview]
Message-ID: <d65957be92ff75db914c6c7af094e656faa2f775.camel@ipfire.org> (raw)
In-Reply-To: <cddbe963-028e-5bd9-4334-f022e8c2948c@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Where is the initscript?
[root(a)rice-oxley ipfire-2.x]# find src/initscripts/ -name nrpe
[root(a)rice-oxley ipfire-2.x]#
On Tue, 2018-05-01 at 15:00 +0200, Peter Müller wrote:
> Install an initscript for the NRPE addon (this was missing
> in the NRPE update patch).
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> lfs/nagios_nrpe | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lfs/nagios_nrpe b/lfs/nagios_nrpe
> index 369f9335d..aa9a773be 100644
> --- a/lfs/nagios_nrpe
> +++ b/lfs/nagios_nrpe
> @@ -89,5 +89,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>
> cd $(DIR_APP) && make $(MAKETUNING)
> cd $(DIR_APP) && make install
> +
> + #install initscripts
> + $(call INSTALL_INITSCRIPT,nrpe)
> +
> @rm -rf $(DIR_APP)
> @$(POSTBUILD)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlrwKyAACgkQgHnw/2+Q
CQfQ3A/8CRgmZehpS0lIyKcpp42MH7WogkuXuFO8ii62UQH6hoCQSFZ8AlxQgTHs
F9ef5qX95W8qxVFoMZGWRHYNBt55MNLumR6HoXShkFaJaR1ZNUqWgb8kpK8H6SbF
fLDYpZj7BIAoELPGDG06JBiT0I3rdHh246vmdWcgA4T4nmnjVcdIkVwHzlcoP54Y
JqP2ODcQk6SbrrcKk+lLTSGu768O+HET8c8UG//EbIjFc/AN8AuWSJvM+iKqCtsx
+LFcy87pMcDeIzGIOY5Pr6Y+Gn4jgLOKK6QRa3p7AN3llQv8prPK0/XFPlFQ5Zg9
M5F8T0mJSEMxRi4tcXJZaGRH8/rMxWpykEvXLVrCx4VQ6DqQ5lD0HDSxOnOkB/tD
/clpU6qh1D7dfmS/onY8gXZfloGubZSlimn1bnQRf1L9HTQ9btKR0iYiLqfsyx0E
+oTheoRET61yDVJIiO5rsDCs7i6sn/0SDfOaxGYYFqOGOP6pdknpWjCXvykzk7cF
G5Z6Y3i0HrBqZKEkmpSrJq+Y6mQ8hF2znQtfzKhnZp+b21Tk7ztHYdxMAQqZa10g
GQtyL0h/JCNvBq4IDws/5VCDshpCLgqJ36kD81JHbh2O6k8zxQZc43flWnEkUulJ
Coo4VNCoSqkOsQ7ILIecs53kDjCIUbyFONPhQeLv3SJBWnDlLrc=
=hITZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-05-07 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 13:00 Peter Müller
2018-05-07 10:32 ` Michael Tremer [this message]
2018-05-07 14:34 ` [PATCH v2] " Peter Müller
2018-05-07 14:56 ` [PATCH v3] " Peter Müller
2018-05-09 13:53 ` Michael Tremer
2018-05-09 19:59 ` [PATCH v4] " Peter Müller
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=d65957be92ff75db914c6c7af094e656faa2f775.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@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