From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Never mind ...
Date: Sun, 07 Nov 2004 15:59:43 -0500 [thread overview]
Message-ID: <m3lldd74u8.fsf@asfast.com> (raw)
In-Reply-To: <20041107135411.13387.qmail@e25d0edd6a570d.315fe32.mid.smarden.org>
Gerrit Pape <pape@smarden.org> writes:
> 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.
Well, all I noticed when I started poking around in the directory is
that I got 'access denied' errors on some of the files there. At that
point, I deleted the entire directory and recreated it, and then
everything worked. I assume that this has to do with ownership or file
permissions.
I'm sorry that I can't give you more info. Next time something like
this happens, I'll do a better job of collecting data before changing
anything.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
prev parent reply other threads:[~2004-11-07 20:59 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
2004-11-07 20:59 ` Lloyd Zusman [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=m3lldd74u8.fsf@asfast.com \
--to=ljz@asfast.com \
/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).