From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Runit on sl3
Date: Fri, 26 May 2006 16:18:11 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0605261604050.18848@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <7231C15EAC2F164CA6DC326D97493C8B01C1DE38@exchange35.fed.cclrc.ac.uk>
On Fri, 26 May 2006, Nandakumar, R (Raja) wrote:
> I would like to know if there have been any known problems while using
> the runit class of commands on scientific linux. Two of the problems we
> see are :
>
> 1. runsv does not automatically fork and make itself a background job.
Why do you see that as a problem? runsv should only be run by runsvdir,
which will then wait for it to complete.
> 2. runsv and runsvdir occasionally die
Do you know why they do? My guess is that you have had severe memory
overcommitment, and they are being killed by the "Out of Memory" killer of
the linux kernel. They won't have been the only processes killed (but
perhaps they would be the most noticable ones*).
But if there's any other cause of them dying, then I'm
sure Gerrit would be interested to know.
---
Charlie
* runsv will be replaced automatically, but service will be in down state
if there is a "down" file, whereas it might have been running when the
runsv died/was killed. Hence, death of runsv might be quite noticeable.
next prev parent reply other threads:[~2006-05-26 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 9:56 Nandakumar, R (Raja)
2006-05-26 20:18 ` Charlie Brady [this message]
2006-05-26 20:59 ` Nandakumar, R (Raja)
2006-05-26 22:43 ` Charlie Brady
2006-05-26 22:47 ` Nandakumar, R (Raja)
2006-05-26 22:59 ` Charlie Brady
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=Pine.LNX.4.61.0605261604050.18848@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--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).