Nagios Remote Plug-In Executor

Edit Package nrpe
http://www.nagios.org/

NRPE can be used to run nagios plug-ins on a remote machine for
executing local checks.
This package contains the software for NRPE server.
It could be run by inet-daemon or as stand-alone daemon

Refresh
Refresh
Source Files
Filename Size Changed
README.SUSE 0000001429 1.4 KB
README.SUSE.systemd-addon 0000000275 275 Bytes
check_nrpe.cfg 0000000867 867 Bytes
nagios-nrpe-SuSEfirewall2 0000000382 382 Bytes
nagios-nrpe-rpmlintrc 0000000293 293 Bytes
nrpe-3.2.1-dh.h 0000002181 2.13 KB
nrpe-3.2.1-static_dh_parameters.patch 0000001818 1.78 KB
nrpe-3.2.1.tar.bz2 0000492190 481 KB
nrpe-implicit_declaration.patch 0000000322 322 Bytes
nrpe-improved_help.patch 0000001365 1.33 KB
nrpe.8 0000001875 1.83 KB
nrpe.changes 0000027932 27.3 KB
nrpe.init 0000003319 3.24 KB
nrpe.spec 0000015134 14.8 KB
nrpe.xml 0000000315 315 Bytes
nrpe_check_control.patch 0000000538 538 Bytes
usr.sbin.nrpe 0000001319 1.29 KB
Revision 66 (latest revision is 94)
Lars Vogdt's avatar Lars Vogdt (lrupp) committed (revision 66)
- add nrpe.xml snipplet for firewalld
- still ship nrpe snipplet for SuSEfirewalld for now
- use systemd files directly from upstream:
  + drop Requires=var-run.mount line from service file 
  + drop nrpe.service
  + drop nrpe.socket
  + do not create tmpfiles.d/nrpe in spec any longer
- handle migration from /etc/nagios/nrpe.cfg to /etc/nrpe.cfg also 
  for systemd case (triggerun)
- increase warn/crit level for processes to 350/400 in a default 
  installation
- added patch and dh.h file to NOT re-calculate dh.h parameters 
  during each build (for reproducable builds). 
  Can be enable/disable by setting the 'reproducable' build 
  condition. Default is: "on" for now
  + nrpe-3.2.1-static_dh_parameters.patch
  + nrpe-3.2.1-dh.h
- use _rundir and _tmpfilesdir macros everywhere
- do not create nagios user/group during install on (open)SUSE
  systems and rely on the files section here instead
Comments 1

Heiko Jansen's avatar

The inclusion of the "%{release}" makro in the "Provides" / "Obsoletes" fields of the package metadata means that on each and every rebuild there's a diff to the previous build and the new build is published even when there are no real changes. That causes quite some "noise" for me with SuSE Manager quite often telling me I had updates to approve of. I'm not exactly sure if %{version} wouldn't be sufficient but I thought I could at least give a heads up here ...

openSUSE Build Service is sponsored by