supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Yoshinori Sato <yo-satoh@sios.com>
To: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@ntlworld.com>
Cc: supervision@list.skarnet.org
Subject: Re: runit don't restart service.
Date: Wed, 25 Jul 2018 17:53:04 +0900	[thread overview]
Message-ID: <CAL_XjKVLJkxb_78uhqMsK4p3A1b4jYBLiVyFQh1OX9J-E=J0Ug@mail.gmail.com> (raw)
In-Reply-To: <487edab4-cee2-d3f6-08bc-b2535ca891f7@NTLWorld.COM>

OK.

I understood it.
I will try it again.

Thanks.

2018-07-25 17:35 GMT+09:00 Jonathan de Boyne Pollard
<J.deBoynePollard-newsgroups@ntlworld.com>:
> Yoshinori Sato:
>
>> root 10647 10592 0 7月13 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkcheck
>>
>> terminate service
>> [root@nodeA ec2-user]# kill 10647 12521
>>
> That is not terminating a service.  That is terminating the service
> supervision subsystem.  If you kill the process that actually does the
> restarting, you really should not expect that process to then restart
> anything.  The behaviour of runsv in response to SIGTERM is documented in
> its manual; as are the ways to properly tell it to terminate a service, as
> opposed to what you did here.
>
> Use the runit manual in preference to the LifeKeeper manual here, too.  In
> particular learn the use of runit commands like
>
>     # /opt/LifeKeeper/sbin/sv status /opt/LifeKeeper/etc/service/*
>
> rather than the clumsy and error-prone grepping of the process list that is
> given in the LifeKeeper manual.
>


      reply	other threads:[~2018-07-25  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  6:29 Yoshinori Sato
2018-07-25  8:35 ` Jonathan de Boyne Pollard
2018-07-25  8:53   ` Yoshinori Sato [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='CAL_XjKVLJkxb_78uhqMsK4p3A1b4jYBLiVyFQh1OX9J-E=J0Ug@mail.gmail.com' \
    --to=yo-satoh@sios.com \
    --cc=J.deBoynePollard-newsgroups@ntlworld.com \
    --cc=supervision@list.skarnet.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).