From: EuAndreh <eu@euandre.org>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix@gnu.org
Subject: Re: Manual: why not restart service over killing the process
Date: Sat, 28 Nov 2020 18:51:07 -0300 [thread overview]
Message-ID: <87h7p9m9pw.fsf@euandre.org> (raw)
In-Reply-To: <87blfhtrjk.fsf@cbaines.net>
Christopher Baines <mail@cbaines.net> writes:
> You're sort of right, but you've got the downsides the wrong way around.
>
> The key bit with the kill call is the SIGHUP but, not that it's not
> SIGKILL. The current situation won't kill the NGinx process, but instead
> just get it to reload the certificate (at least that's the intention).
>
> The restart action would "kill" the process, in that it would send it
> SIGTERM and the the shepherd would start a new NGinx process, and this
> has the potential of interrupting whatever is using NGinx.
>
> Does that make sense?
Hmm, great answer!
Makes sense, and the SIGHUP signal really is indeed better for this
case. Thanks for the informational response!
next prev parent reply other threads:[~2020-11-28 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 14:58 Manual: why not restart service over killing the process EuAndreh
2020-11-28 15:44 ` Christopher Baines
2020-11-28 21:51 ` EuAndreh [this message]
2020-11-29 14:01 ` Jason Conroy
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7p9m9pw.fsf@euandre.org \
--to=eu@euandre.org \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).