supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Dean Hall <deanpence@gmail.com>
Subject: Re: runit on debian sid success, and questions
Date: Tue, 18 Jan 2005 22:59:25 -0500	[thread overview]
Message-ID: <41EDDB1D.30300@gmail.com> (raw)
In-Reply-To: <20050118171303.A27683@recycle.lbl.gov>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

| My problem is not so much putting these daemons under runit,
| it's getting them _out_ of SysV init.  In the case of cron
| and portmap, I ended up simply getting rid of them.

How did you get rid of portmap? Did you get rid of the services for
which it's required? Or did you force them to use a static port?

| I can post my norc (antithesis of cron) script if anyone
| is interested.  It's a ten-line shell script that runs
| the scripts in /etc/cron.daily at three in the morning,
| using sleep and date.

You might check out uschedule <http://www.ohse.de/uwe/uschedule.html>.
It's a decent and simple cron and at replacement.

| I just noticed the ipsvd package yesterday, which is an
| apt-get away.  Whee!  I have started to phase out tcpserver.

For gentoo users out there, I've submitted an ebuild for ipsvd. Right
now it's only available at the bug post:
<http://bugs.gentoo.org/show_bug.cgi?id=76522>.

| I ran into odd runit shutdown behavior on another machine,
| vanilla Pentium (Celeron) with Debian sarge.  I don't have
| the exact message, but it said something like
|
|    power down
|    kernel panic, attempting to kill init!

I got that message too while running runit with Debian (custom install,
not apt-get). I never really researched it, as I knew I'd be switching
to Debian soon--and I haven't converted over to a runit init scheme yet.

| It was quite a trick
| to shut down the machine the first time after that install!
| Something like "/sbin/sysv-init 0" finally did it; telint was
| linked to runit-init, which of course didn't know how to shut
| down the system running under the old paradigm.

Yeah, you have to use the sysv init executable to shut down the machine
the first time. *shrug*


d
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB7dscY5YOge8zySQRAuVHAKCeKdco5hi4/hAtikTzj5ZD3RSSmwCeMr9K
wqB1xykVvYlOqdzBeuQHrXw=
=za/0
-----END PGP SIGNATURE-----


  reply	other threads:[~2005-01-19  3:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19  1:13 Larry Doolittle
2005-01-19  3:59 ` Dean Hall [this message]
2005-01-19 10:03   ` Milan P. Stanic
2005-01-19  6:08 ` Larry Doolittle
2005-01-19 21:09   ` Thomas Schwinge
2005-01-19  6:39 ` Dean Hall
2005-01-23 12:23 ` Gerrit Pape
  -- strict thread matches above, loose matches on Subject: below --
2005-01-19  6:12 Larry Doolittle
2005-01-19 21:07 ` Thomas Schwinge
2005-01-19 21:53   ` Larry Doolittle
2005-01-20 22:55 ` Vincent Danen
2005-01-14 20:08 Larry Doolittle
2005-01-15 16:07 ` 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=41EDDB1D.30300@gmail.com \
    --to=deanpence@gmail.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).