Github messages for voidlinux
 help / color / mirror / Atom feed
From: bahamas10 <bahamas10@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: nagios-4.4.6
Date: Fri, 10 Jul 2020 19:06:40 +0200	[thread overview]
Message-ID: <20200710170640.zwNWWkQJ7Dcnvz-EWwyOtBlbi01GIi7LPQ6g0rcMv6I@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: 1031 bytes --]

New comment by bahamas10 on void-packages repository

https://github.com/void-linux/void-packages/pull/23249#issuecomment-651273455

Comment:
I tested this with:

#### disable and cleanup

```
sudo sv down nagios
sudo rm /var/service/nagios
sudo xbps-remove -y nagios
sudo rm -rf /var/nagios /etc/nagios /etc/sv/nagios
```

#### create and install new package

```
./xbps-src clean nagios
./xbps-src -f pkg nagios
xi nagios
```

#### verify installation

```
$ tree -ug /var/nagios
/var/nagios
├── [_nagios  _nagios ]  rw
└── [_nagios  _nagios ]  spool
    └── [_nagios  _nagios ]  checkresults

3 directories, 0 files
```

#### enable the service

```
sudo ln -s /etc/sv/nagios
```

#### ensure working

```
$ sudo vsv status nagios

   SERVICE              STATE   ENABLED   PID      COMMAND           TIME
 ✔ nagios               run     true      17828    nagios            31 seconds

$ nagiostats | grep PID
Nagios PID:                             17828
```

  parent reply	other threads:[~2020-07-10 17:06 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 [this message]
2020-07-10 23:12 ` 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 ` [PR PATCH] [Closed]: " github-actions

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=20200710170640.zwNWWkQJ7Dcnvz-EWwyOtBlbi01GIi7LPQ6g0rcMv6I@z \
    --to=bahamas10@users.noreply.github.com \
    --cc=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).