From: "David Kaufman" <david@gigawatt.com>
Subject: Re: runit-run install failed - conflict w/unofficial daemontools-run?
Date: Mon, 13 Nov 2006 22:47:23 -0500 [thread overview]
Message-ID: <000601c7079f$9866d8e0$020010ac@cylon> (raw)
In-Reply-To: <00eb01c70760$2f2ece80$020010ac@cylon>
[replying to self]
I, David Kaufman <david@gigawatt.com> wrote:
> I just tried to install runit and runit-run on a Debian sarge setup
> which already has var-qmail, qmail-run, djbdns and daemontools
> installed from http://smarden.org/pape/Debian/ ... using dselect, and
> this was the output:
>
> There already is an SV entry in /etc/inittab [...] you need to remove
> or rename the current SV entry first.
> Installation failed.
>
> [...] looked in [/etc/inittab] and found:
> #-- daemontools-run begin
> SV:123456:respawn:/command/svscanboot
> #-- daemontools-run end
Just found Gerrit's reply to a similar question in the list archives:
http://article.gmane.org/gmane.comp.sysutils.supervision.general/1113
which answers each of my questions:
> Should I just rename the old SV entry in there?
No, grasshopper. runit *replaces* daemontools.
> If so, does it matter what I rename it to?
You (I mean I) should comment (or delete) these daemontools lines *out*
of the inittab before attempting to install runit (though it would be
nice if an install script did that). Do not uninstall the daemotools
debian package though. It may have some binaries your existing
/var/service's (qmail, dbjdns) are using.
> I sure hope the unofficial daemontools-run and runit-run are
> compatible with one another!
{sigh}. runit is backwards-compatible with daemontools.
> Thanks for any suggestion anyone might have to offer!
I'm welcome, me!
-dave
prev parent reply other threads:[~2006-11-14 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 20:13 David Kaufman
2006-11-14 3:47 ` David Kaufman [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='000601c7079f$9866d8e0$020010ac@cylon' \
--to=david@gigawatt.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).