From: Joshua N Pritikin <jpritikin@pobox.com>
Subject: Re: Runit-run and socklog-run upgrades on Debian sid, be careful!
Date: Thu, 23 Mar 2006 12:04:38 +0530 [thread overview]
Message-ID: <20060323063438.GN3082@always.joy.eth.net> (raw)
In-Reply-To: <20060322193831.GC24911@odin.dempsky.org>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Wed, Mar 22, 2006 at 01:38:31PM -0600, Matthew R. Dempsky wrote:
> On Wed, Mar 22, 2006 at 09:23:28AM -0600, Kevin wrote:
> > Runit-run replaces the getty links in /var/service with new ones
> > in /etc/sv. If you're running the upgrade from a getty, the getty will
> > die when its service dir link is removed to be replaced, leaving
> > non-functional services.
>
> Hm, when I upgraded about 30 minutes ago, I saw some weirdness in the
> logs, but my fgetty's didn't die. (I too was upgrading via the
> terminal.)
It probably depends on the speed of the machine. runsvdir polls at
least every 5 seconds so any race condition would be more apparent on a
slow machine.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-23 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 15:23 Kevin
2006-03-22 19:38 ` Matthew R. Dempsky
2006-03-23 6:34 ` Joshua N Pritikin [this message]
2006-04-01 8:31 ` 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=20060323063438.GN3082@always.joy.eth.net \
--to=jpritikin@pobox.com \
/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).