supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jean-Michel Bruenn <jean.bruenn@ip-minds.de>
To: supervision@list.skarnet.org
Subject: Re: hello - hanging services
Date: Tue, 17 Aug 2010 19:24:22 +0200	[thread overview]
Message-ID: <20100817192422.a157e85f.jean.bruenn@ip-minds.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1008171311210.4362@e-smith.charlieb.ott.istop.com>

Hello,

thanks for your answer. Wouldn't it be a good improvement for runit,
if it would take care of hanging tasks, also? There's "run", "finish"
and the "log" stuff - wouldn't it be possible to add "check" as script,
which is running a command all X seconds and if it gets a response it
knows "ah okay, the service is still running" and if it gets no
response "oh, the service seems to have died, let's restart it"?

Of course, totally optional, up to the user whether to use that or not.

Difficult to implement?

Cheers

On Tue, 17 Aug 2010
13:13:55 -0400 (EDT) Charlie Brady
<charlieb-supervise@budge.apana.org.au> wrote:

> 
> On Tue, 17 Aug 2010, Jean-Michel Bruenn wrote:
> 
> > Hey, 
> > 
> > i'm curious what happens with hung(hanging?) services (or zombies) is it
> > possible with runit to detect those and restart the service?
> 
> hung/hanging services and zombies are different things. A zombie is a 
> process which doesn't exist - it's just a process remnant - a status 
> report which the kernel is hanging onto waiting for someone to ask for it. 
> A hung/hanging services is a real process, but one which isn't doing what 
> you want it to do. runit does not detect and restart those. It only 
> restarts processes which have died.


-- 
Jean-Michel Bruenn <jean.bruenn@ip-minds.de>


  parent reply	other threads:[~2010-08-17 17:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 17:08 Jean-Michel Bruenn
     [not found] ` <Pine.LNX.4.64.1008171311210.4362@e-smith.charlieb.ott.istop.com>
2010-08-17 17:24   ` Jean-Michel Bruenn [this message]
2010-08-17 17:38     ` Charlie Brady
2010-08-18 10:57       ` Laurent Bercot
2010-08-18 15:06         ` Jean-Michel Bruenn
2010-08-18 15:23           ` Charlie Brady
2010-08-18 16:02             ` Jean-Michel Bruenn
2010-08-19  5:46               ` Laurent Bercot
2010-08-20 12:24                 ` Nicolás de la Torre
2010-08-20 14:42                   ` Tobia Conforto
2010-08-20 14:59                     ` Charlie Brady
     [not found]                     ` <BB40BB3F77C4402181674BE975669A4F@HEL.local>
2010-08-20 15:11                       ` Rehan
2010-08-20 15:13                         ` Charlie Brady
2010-08-20 15:40                     ` Laurent Bercot

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=20100817192422.a157e85f.jean.bruenn@ip-minds.de \
    --to=jean.bruenn@ip-minds.de \
    --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).