From: Gerrit Pape <pape@smarden.org>
Subject: Re: Migrating from daemontools
Date: Fri, 12 May 2006 15:23:40 +0000 [thread overview]
Message-ID: <20060512152340.13033.qmail@d3387fbf9fcfb4.315fe32.mid.smarden.org> (raw)
In-Reply-To: <44627A0A.6030404@robinbowes.com>
On Thu, May 11, 2006 at 12:40:58AM +0100, Robin Bowes wrote:
> I'm about to migrate to runit from daemontools (for licensing reasons).
>
> Can I just confirm that it is as simple as :
>
> 1. Install runit
> 2. Create /var/service
> 3. Add to start up (inittab on linux or /etc/rc.local on FreeBSD)
> 4. Re-read inittab (Linux) or reboot (FreeBSD)
Yes, I would replace the invocation of svscanboot with runsvdir-start
though, and have only runsvdir run. Then move the services from
/service/ into /var/service/.
> Am I right in thinking that my current scripts should run OK using runsv
> instead of supervise?
Yes, no changes are required as long as you have the daemontools
programs still around.
> Are there runit equivalents of all daemontools binaries, specifically
> tai64nlocal (I am assuming that sv == svc, svlogd == multilog) ?
Not all, fghack is missing. And tai64n/local doesn't have an equivalent
in runit as svlogd can be told to write human-readable, sortable
timestamps to the logs with the -tt switch. So this post-processing
isn't necessary.
svscan, svscanboot, readproctitle -> runsvdir
svc, svstat, svok -> sv
supervise -> runsv
envdir, enduidgid, pgrphack, setlock, setuidgid, softlimit -> chpst
multilog -> svlogd
Regards, Gerrit.
prev parent reply other threads:[~2006-05-12 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 23:40 Robin Bowes
2006-05-11 9:29 ` Robin Bowes
2006-05-12 15: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=20060512152340.13033.qmail@d3387fbf9fcfb4.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).