From: Kevin <spamite@ev1.net>
Cc: supervision@list.skarnet.org
Subject: Re: init signals and touching files
Date: Tue, 01 Mar 2005 08:29:46 -0600 [thread overview]
Message-ID: <1109687386.3657.5.camel@localhost> (raw)
In-Reply-To: <f02866722af0177e608b2f6b82471bd4@annvix.org>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
> The other issue I have is that runit-init (which I've renamed to init)
> always wants to shut down. If I do "init 6", I expect it to reboot,
> but it halts the system. I don't think runit should care that
> runit-init is now called init, but I don't know. I did write little
> wrapper scripts to replace the SysVinit reboot/halt scripts (so that
> you can set a time and it sends out a wall message), but the last thing
> called is "init 0" for halt and "init 6" for reboot but in all cases it
> shuts down. I don't know why though. Any ideas on this?
I'm wondering somewhat with your stage 3 script looks like. I've only
ever had the shutdown troubles you describe on a FreeBSD box that was
using the port, which had some somewhat goofy stage scripts. I took the
useful bits from my Debian GNU/Linux stage 3 scripts to fix it up, and
it now shutsdown and reboots like it is supposed to.
> Beyond those two issues, using runit rocks. I can deal with the r/o
> filesystem issue by adding some documentation noting the fact that this
> is a problem and that there is no real damage to anything (because it's
> all mounted r/o), it's just ugly and not very well handled (with
> SysVinit, this has never been a problem). And it won't actually affect
> me again because now I mount those drives from rc.local *after* I
> manually modprobe sata_promise.
This sounds like you either need to place the driver within the kernel,
or place sata_promise in /etc/modules... I'm guessing you're able to
boot this drive at all due to an initrd or similar..
> The lack of a reboot issue is big though because it makes doing remote
> administration (ie. a reboot due to a kernel upgrade) extremely
> problematic.
Check out your stage 3 script. Something is wrong there, I'm thinking.
Did you install via a distribution package, or from the slashpackage?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-01 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 15:46 Vincent Danen
2005-03-01 14:29 ` Kevin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-28 3:59 Vincent Danen
2005-03-04 15:56 ` 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=1109687386.3657.5.camel@localhost \
--to=spamite@ev1.net \
--cc=supervision@list.skarnet.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).