supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: mike@mikebell.org
Subject: Re: "djbdns" under "runit" (Debian)?
Date: Sun, 15 May 2005 19:08:00 -0700	[thread overview]
Message-ID: <20050516020441.GA986@mikebell.org> (raw)
In-Reply-To: <20050516005737.GA8379@harfang.homelinux.org>

On Mon, May 16, 2005 at 02:57:37AM +0200, Gilles wrote:
> Wouldn't it be sufficient to just add "runit" as an alternative to
> "daemontools" in the dependency list?

Not unless the symlinks came with it. runit programs will behave
differently when called using daemontools names. One could easily
however have a "legacy-free" runit and a separate package that provided
"daemontools" and the symlinks.

> What you suggest enables using the daemontools names for calling the 
> runit programs (in order to "provide" a daemontools interface). [Am I 
> correct?]

See above.

> I just want to use runit's names for calling runit's programs. [Unless
> the djbdns software somehow relies on the actual supervision software
> used (?).]

You can also just change the scripts, but then tinydns-conf and the like
don't work and you need to do a little manual vi work after.

> What do you mean by "manually insert daemontools as installed"?
> Could you please be more explicit?

Basically shut debian up by lying to it and telling it that daemontools
is installed. There's probably a mechanism for doing it properly, but I
just use vi to tell it that daemontools is installed and has no files.


  reply	other threads:[~2005-05-16  2:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  0:19 Gilles
2005-05-16  0:30 ` mike
2005-05-16  0:57   ` Gilles
2005-05-16  2:08     ` mike [this message]
2005-05-16 19:55       ` Csillag Tamás
2005-05-16  1:13   ` Charlie Brady
2005-05-16  1:53     ` Gilles
2005-05-16  2:22     ` mike
2005-05-16 19:43 ` TheOldFellow
2005-05-17 13:20   ` Gilles
2005-05-17 13:49     ` Gerrit Pape

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=20050516020441.GA986@mikebell.org \
    --to=mike@mikebell.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).