supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: yoppo@jippii.fi
Subject: about runit...
Date: Sun, 26 Sep 2004 23:29:37 +0300 (EEST)	[thread overview]
Message-ID: <4309480.1096230577999.JavaMail.yoppo@jippii.fi> (raw)

Hi!

First I must say that I started using runit about month ago and I must 
say I am pretty pleased with it. Now I think I found small bug in it. 
When acpi is disabled (acpi=off at lilo append) I got kernel panic at 
end of the shutdown/reboot process:

....
-runit: power off...
Power down.
Kernel panic: Attempted to kill init!

Off course this actually doesn't matter much but I think it should cause 
this when acpi disabled.

Then secondly isn't there any mechanism to detect / remove (or 
something) faulty init scripts or does runsv keep trying to start it 
forever? I just don't like the idea that some process may stay restartig 
forever in the background if (for example) daemon has wrong parameters 
and won't start.

And other question remotely related to the previous one. Is there any 
way to make init script for processes that aren't daemons. Like setting 
clock / keyboard stuff?

And the last one. Is there anyway to log the runsv errors.
At least if I execute it from console it gives some error messages if 
error appears. But if same error occures at boot time I can't find any 
error from any system logs. Of course I can log the init daemons with 
svlog but can't find a way to log for runsv...

But anyway great piece of software much better than sysvinit!

Thanks in advance for replying.



-- 

__
Älä maksa tekstiviesteistä! Saunalahden Tekstari-GSM-liittymällä lähetät tekstiviestit maksutta kaikkiin liittymiin (1000 kpl/kk).
http://saunalahti.fi



                 reply	other threads:[~2004-09-26 20:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4309480.1096230577999.JavaMail.yoppo@jippii.fi \
    --to=yoppo@jippii.fi \
    /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).