From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Fix the status check of unbound
Date: Mon, 12 Jun 2017 18:06:41 +0100 [thread overview]
Message-ID: <1497287201.21214.25.camel@ipfire.org> (raw)
In-Reply-To: <20170610105644.28854-1-christian+ipfire@kohlsted.de>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Hello Christian,
thank you very much for your submissing.
What is the bug this is trying to fix? I never noticed that something is not
working okay here.
Best,
-Michael
On Sat, 2017-06-10 at 12:56 +0200, Christian Kohlstedde wrote:
> From: Christian Kohlstedde <christian(a)kohlsted.de>
>
> ---
> src/initscripts/system/unbound | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/src/initscripts/system/unbound b/src/initscripts/system/unbound
> index 7437d93b8..04de3c1e0 100644
> --- a/src/initscripts/system/unbound
> +++ b/src/initscripts/system/unbound
> @@ -457,7 +457,7 @@ disable_dnssec() {
> case "$1" in
> start)
> # Print a nicer messagen when unbound is already running
> - if pidofproc -s unbound; then
> + if pidofproc -s /usr/sbin/unbound; then
> statusproc /usr/sbin/unbound
> exit 0
> fi
> @@ -503,7 +503,7 @@ case "$1" in
>
> update-forwarders)
> # Do not try updating forwarders when unbound is not running
> - if ! pgrep unbound &>/dev/null; then
> + if pidofproc -s /usr/sbin/unbound; then
> exit 0
> fi
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-12 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 10:56 Christian Kohlstedde
2017-06-12 17:06 ` Michael Tremer [this message]
2017-06-12 18:56 ` Christian Kohlstedde
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=1497287201.21214.25.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