From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: nagios-4.4.6
Date: Sun, 01 May 2022 04:13:50 +0200 [thread overview]
Message-ID: <20220501021350.ikdl9l049a5ii-7VcNcUwsMBP0JabwPOQb702fL9yO0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23249@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
There's a closed pull request on the void-packages repository
New package: nagios-4.4.6
https://github.com/void-linux/void-packages/pull/23249
Description:
`nrpe` and `monitoring-plugins` are already available as packages... this changes adds the nagios core itself into the set of available packages.
4.4.6 is the latest release available.
### Testing
I built the package and installed it with:
```
./xbps-src -f pkg nagios
xi nagios
```
I then enabled the service:
```
ln -s /etc/sv/nagios /var/service
```
And verified it was running with:
```
$ sudo cat /var/service/nagios/supervise/pid
30982
$ nagiostats
Nagios Stats 4.4.6
Copyright (c) 2003-2008 Ethan Galstad (www.nagios.org)
Last Modified: 2020-04-28
License: GPL
CURRENT STATUS DATA
------------------------------------------------------
Status File: /var/nagios/status.dat
Status File Age: 0d 0h 0m 3s
Status File Version: 4.4.6
Program Running Time: 0d 0h 0m 3s
Nagios PID: 30982
```
Notice the PID in the `nagiostats` output matches the PID according to runit.
prev parent reply other threads:[~2022-05-01 2:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23249@inbox.vuxu.org>
2020-07-09 15:59 ` [PR REVIEW] " sgn
2020-07-09 16:00 ` sgn
2020-07-09 16:02 ` sgn
2020-07-09 16:03 ` sgn
2020-07-09 16:03 ` sgn
2020-07-09 18:12 ` bahamas10
2020-07-09 18:16 ` bahamas10
2020-07-09 18:16 ` bahamas10
2020-07-09 18:17 ` bahamas10
2020-07-09 18:17 ` bahamas10
2020-07-09 21:27 ` bahamas10
2020-07-09 21:27 ` bahamas10
2020-07-09 21:41 ` bahamas10
2020-07-10 0:06 ` sgn
2020-07-10 0:12 ` sgn
2020-07-10 0:14 ` sgn
2020-07-10 0:15 ` sgn
2020-07-10 0:21 ` sgn
2020-07-10 17:00 ` bahamas10
2020-07-10 17:00 ` bahamas10
2020-07-10 17:03 ` bahamas10
2020-07-10 17:04 ` bahamas10
2020-07-10 17:06 ` bahamas10
2020-07-10 23:12 ` [PR REVIEW] " sgn
2020-07-10 23:15 ` sgn
2020-07-12 0:29 ` bahamas10
2020-07-12 0:36 ` bahamas10
2020-07-12 0:39 ` bahamas10
2020-10-31 5:26 ` sgn
2020-11-22 1:01 ` [PR PATCH] [Updated] " bahamas10
2020-11-22 1:02 ` bahamas10
2020-11-22 1:24 ` ericonr
2020-11-22 1:38 ` [PR PATCH] [Updated] " bahamas10
2022-04-17 2:06 ` github-actions
2022-05-01 2:13 ` github-actions [this message]
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=20220501021350.ikdl9l049a5ii-7VcNcUwsMBP0JabwPOQb702fL9yO0@z \
--to=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).