supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: Runit-run and socklog-run upgrades on Debian sid, be careful!
Date: Sat, 1 Apr 2006 08:31:45 +0000	[thread overview]
Message-ID: <20060401083145.11686.qmail@8fc3cd8af8c441.315fe32.mid.smarden.org> (raw)
In-Reply-To: <200603220923.57498.spamite@ev1.net>

On Wed, Mar 22, 2006 at 09:23:50AM -0600, Kevin wrote:
> I discovered this morning when upgrading my sid box, that runit-run and 
> socklog-run both failed in interesting ways.

socklog-run has been fixed since, it hasn't been tested enough, but
that's what Debian/unstable can catch.

> 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.  I was able to get in via ssh and fix the links 
> so that the getty's worked, and also tested not-fixing them and letting 
> dpkg --configure -a finish the job.  Both worked.  

I'll have to take a look at that.

> I'm not sure there are good ways to get around this on an upgrade of these 
> packages, so I'm uncertain if I should try to file a bug report.  Any 
> thoughts?

Bug reports to the Debian BTS are just fine for such things.

Thanks, Gerrit.


      parent reply	other threads:[~2006-04-01  8:31 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
2006-04-01  8:31 ` 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=20060401083145.11686.qmail@8fc3cd8af8c441.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).