From: Laurent Bercot <ska-supervision@skarnet.org>
To: supervision@list.skarnet.org
Subject: Re: runsv spinning 100% CPU (was Re: runsv and EAGAIN)
Date: Wed, 18 Feb 2009 01:09:46 +0100 [thread overview]
Message-ID: <20090218000946.GA4679@skarnet.org> (raw)
In-Reply-To: <loom.20090210T123504-804@post.gmane.org>
> Another option would be to have runsv print out an error message like
> 'supervise/control exists but is not a fifo.' and exit with 111. This
> may be better than forcefully removing a file.
I think this is the wiser choice. When in doubt, exit with an error
message and let the administrator handle it.
However, I'd exit 100, not 111, because the problem is structural,
not temporary: it's not that some resource is unavailable, it's that
runsv is used incorrectly (i.e. supervise/ has been tampered with).
--
Laurent
prev parent reply other threads:[~2009-02-18 0:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 20:46 runsv and EAGAIN Charlie Brady
2008-07-12 1:27 ` Charlie Brady
2008-07-12 16:07 ` Dražen Kačar
2008-07-13 2:46 ` Charlie Brady
2009-01-20 23:21 ` runsv spinning 100% CPU (was Re: runsv and EAGAIN) Charlie Brady
2009-02-10 12:41 ` Gerrit Pape
2009-02-18 0:09 ` Laurent Bercot [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=20090218000946.GA4679@skarnet.org \
--to=ska-supervision@skarnet.org \
--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).