Re: runit on debian sid success, and questions

[Larry Doolittle <ldoolitt@recycle.lbl.gov>]

> > The only (non-kernel) daemons left running _not_ under runsvdir
> > are udevd, portmap, and gconfd-2.  Vixie cron and I aren't getting
> > along very well at the moment, it's not running at all.  :-p
> 
> See here for examples for portmap and Debian's cron:

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.

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.

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

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!

then the disks spun down, but the video kept going.
It then needed me to reset or power down.  Of course, this
machine powered down normally with stock debian sarge init.

For that installation, I simply used "apt-get install runit-init"
once I had the basics tested under runit.  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.  I think I saw
a message giving hints about this as part of the apt-get, but
I blew it off a little too lightly.

    - Larry