From: Gerrit Pape <pape@smarden.org>
Subject: Re: Never mind ... (Was: When running ruby scripts, runsv tightly loops)
Date: Sun, 7 Nov 2004 13:55:30 +0000 [thread overview]
Message-ID: <20041107135411.13387.qmail@e25d0edd6a570d.315fe32.mid.smarden.org> (raw)
In-Reply-To: <m31xf68bs8.fsf@asfast.com>
On Sun, Nov 07, 2004 at 12:32:07AM -0500, Lloyd Zusman wrote:
> It turns out that there was a file permissions problem within the runit
> directory structure for managing my ruby daemon. Once I corrected it,
> runsv stopped looping. Therefore, this had nothing to do with the ruby
> interpreter.
Hm, if runsv has trouble starting the run script, it should pause for a
second before retrying, and not take up a high percentage of cpu. Can
you say what exactly was the permissions problem?
Thanks, Gerrit.
next prev parent reply other threads:[~2004-11-07 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 5:10 When running ruby scripts, runsv tightly loops Lloyd Zusman
2004-11-07 5:32 ` Never mind ... (Was: When running ruby scripts, runsv tightly loops) Lloyd Zusman
2004-11-07 13:55 ` Gerrit Pape [this message]
2004-11-07 20:59 ` Never mind Lloyd Zusman
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=20041107135411.13387.qmail@e25d0edd6a570d.315fe32.mid.smarden.org \
--to=pape@smarden.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).