From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] update nagios_nrpe to 3.2.1
Date: Mon, 23 Apr 2018 10:27:18 +0100 [thread overview]
Message-ID: <1524475638.1637848.210.camel@ipfire.org> (raw)
In-Reply-To: <5684f8f2-d132-39a3-86e6-22918cecb22c@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]
Hello,
does this patch not change anything in the rootfiles at all?
If you have any questions, Matthias can help :)
Best,
-Michael
On Sat, 2018-04-21 at 19:04 +0200, Peter Müller wrote:
> Update NRPE to 3.2.1, which fixes various security vulnerabilities
> and bugs (changelog is available at:
> https://github.com/NagiosEnterprises/nrpe/blob/master/CHANGELOG.md).
>
> Due to changes in ./configure, some options such as initsystem (sysV)
> need to be specified now. Also, simple "make" does not exist anymore
> and must be replaced by "make all".
>
> This fixes #11700 and partly addresses #11551.
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> lfs/nagios_nrpe | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/lfs/nagios_nrpe b/lfs/nagios_nrpe
> index 369f9335d..bebb80144 100644
> --- a/lfs/nagios_nrpe
> +++ b/lfs/nagios_nrpe
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 2.12
> +VER = 3.2.1
>
> THISAPP = nrpe-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = nagios_nrpe
> -PAK_VER = 4
> +PAK_VER = 5
>
> DEPS = "nagios-plugins"
>
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = b2d75e2962f1e3151ef58794d60c9e97
> +$(DL_FILE)_MD5 = 8997e195fea93cdceb8c7ed8ac1d43bc
>
> install : $(TARGET)
>
> @@ -80,14 +80,15 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> cd $(DIR_APP) && ./configure \
> --prefix=/usr \
> --libexecdir=/usr/lib/nagios \
> + --sysconfdir=/etc/nagios \
> + --with-init-type=sysv \
> --with-nrpe-user=nobody \
> --with-nrpe-group=nobody \
> --with-nagios-user=nobody \
> - --with-nagios-group=nobody \
> - --enable-command-args \
> - ac_cv_lib_wrap_main=no
> + --with-nagios-group=nobody
>
> - cd $(DIR_APP) && make $(MAKETUNING)
> + cd $(DIR_APP) && make all $(MAKETUNING)
> cd $(DIR_APP) && make install
> + cd $(DIR_APP) && make install-config
> @rm -rf $(DIR_APP)
> @$(POSTBUILD)
next prev parent reply other threads:[~2018-04-23 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 17:04 Peter Müller
2018-04-23 9:27 ` Michael Tremer [this message]
2018-04-23 14:12 ` Peter Müller
2018-04-23 14:36 ` Michael Tremer
2018-04-29 8:20 ` [PATCH v2] " Peter Müller
-- strict thread matches above, loose matches on Subject: below --
2017-12-08 15:01 [PATCH] " 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=1524475638.1637848.210.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