From: Gerrit Pape <pape@smarden.org>
Subject: Re: runit on Debian vserver (related to #306390)
Date: Mon, 24 Jul 2006 10:02:40 +0000 [thread overview]
Message-ID: <20060724100240.29400.qmail@7219b380d40f54.315fe32.mid.smarden.org> (raw)
In-Reply-To: <200607201724.32202.bernhard@intevation.de>
On Thu, Jul 20, 2006 at 05:24:28PM +0200, Bernhard Reiter wrote:
> yesterday I ran in the same problem as Debian bug #306390
> with runit-1.0.5-3.
> I have just run into the same problem with runit 1.5.0-1 (Debian
> stable).because the vserver was set up already I thought it was a runit bug.
> My other administrator spend quite some time for it,
> so the bug is not closed from my point of view.
>
> To close it, I suggest to add a hint when telinit q (aka kill -s HUP 1) fails:
>
> "You might be in a vserver environment where telinit q does not work.
> A workaround is to comment out kill -s HUB 1 in the postinst script
> and start runit differently.
> Another workaround one is to make the vserver recognise
> telinit and use inittab to start things (initstyle plain)."
>
> Of course, in case of failure the postinst should remove
> the inittab entry again, to avoid problems in the next run.
Ok, thanks for the hint, I'll see what I can do.
> On my installation the problem is solved,
> but it took a bit of time to find the problem and I would save others
> the time with this hint.
>
> Thanks a lot for runit, I find it a nice software with well written
> documentation and Free Software.
Thanks, Gerrit.
prev parent reply other threads:[~2006-07-24 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060719143952.BD73418EE4C@kolab.intevation.de>
2006-07-20 15:24 ` Bernhard Reiter
2006-07-24 10:02 ` 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=20060724100240.29400.qmail@7219b380d40f54.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).