supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Vincent Danen <vdanen@linsec.ca>
Subject: Re: runit upgrades and halt rather than reboot
Date: Sat, 11 Feb 2006 12:44:45 -0700	[thread overview]
Message-ID: <20060211194445.GL1391@annvix.org> (raw)
In-Reply-To: <m3u0b5677z.fsf@multivac.cwru.edu>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

* Paul Jarc <prj@po.cwru.edu> [2006-02-11 14:11:21 -0500]:

> Vincent Danen <vdanen@linsec.ca> wrote:
> > [root@cerberus sbin]# cp init init.org
> > [root@cerberus sbin]# ls -i init init.org
> > 6374308 init*  6301334 init.org*
> 
> Make a hard link instead of a copy:
> # ln init init.org

Nice that works, thanks.  Forgot about hard links.

Anyways, it still doesn't work.  Tried a bunch of times and a bunch of
different things:

1) cp /sbin/init to /sbin/init.old before upgrade; use reboot
2) cp /sbin/init to /sbin/init.old before upgrade; use init.old 6
3) ln /sbin/init to /sbin/init.old before upgrade; use reboot
4) ln /sbin/init to /sbin/init.old before upgrade; use init.old 6

in all cases, this didn't work.

I was also mistaken in an earlier post... I do not move runit to init,
but rather runit-init to init (runit stays as is).  So thinking that
might have something to do with it, I moved runit to init and then it
just plain old wouldn't let me do anything (fatal: needs to be process 1
or something similar); got that from running "runit 6", "init 6", and
"reboot".  So I think I need to have runit-init remain as init and have
it exec runit.

Could that be part of the problem?  If so, why won't runit behave if
it's renamed to init?

-- 
Annvix - Secure Linux Server: http://annvix.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}
Wasting time like it was free...

[-- Attachment #2: Type: application/pgp-signature, Size: 186 bytes --]

  reply	other threads:[~2006-02-11 19:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  4:20 Vincent Danen
2006-02-03 15:40 ` Gerrit Pape
2006-02-03 16:45   ` Vincent Danen
2006-02-03 16:55     ` Gerrit Pape
2006-02-03 17:04       ` Vincent Danen
2006-02-11 19:03       ` Vincent Danen
2006-02-11 19:11         ` Paul Jarc
2006-02-11 19:44           ` Vincent Danen [this message]
2006-02-13 14:44             ` Gerrit Pape
2006-02-14  4:08               ` Vincent Danen
2006-02-14  5:22                 ` Joshua N Pritikin
2006-02-14  5:42                 ` copy runit-init to /sbin/init or not Alex Efros
2006-02-14  6:04                   ` Vincent Danen
2006-02-14 14:08                     ` Alex Efros
2006-02-14 18:49                       ` Vincent Danen

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=20060211194445.GL1391@annvix.org \
    --to=vdanen@linsec.ca \
    /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).