From: Gerrit Pape <pape@smarden.org>
Subject: Re: "bug" in runit's runsvdir
Date: Sat, 1 Apr 2006 08:23:14 +0000 [thread overview]
Message-ID: <20060401082314.11331.qmail@55cb31a6acae07.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20060325225919.GE7784@odin.dempsky.org>
On Sat, Mar 25, 2006 at 04:59:19PM -0600, Matthew R. Dempsky wrote:
> runit's runsvdir stat(2)s the directory it's passed to determine if new
> services have been added or removed, but this doesn't handle the case of
> an existing symlink being changed to point to a different service.
>
> Reading runsvdir's man page, it doesn't say anything to imply that this
> operation should be handled, but I believe this differs in behavior from
> svscan from the daemontools package, so perhaps the difference should
> at least be documented?
Yes, it differs and should be documented, I also happened to run into
this.
Thanks, Gerrit.
prev parent reply other threads:[~2006-04-01 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 22:59 Matthew R. Dempsky
2006-04-01 8:23 ` Gerrit Pape [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=20060401082314.11331.qmail@55cb31a6acae07.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).