From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1883
Path: news.gmane.org!not-for-mail
From: Lloyd Zusman <ljz@asfast.com>
Newsgroups: gmane.comp.sysutils.supervision.general
Subject: Recommended steps for upgrading?
Date: Sat, 28 Jun 2008 15:11:40 -0400
Organization: Take a hippopotamus to lunch today.
Message-ID: <87y74pwf0z.fsf@asfast.com>
NNTP-Posting-Host: lo.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: ger.gmane.org 1214680325 23263 80.91.229.12 (28 Jun 2008 19:12:05 GMT)
X-Complaints-To: usenet@ger.gmane.org
NNTP-Posting-Date: Sat, 28 Jun 2008 19:12:05 +0000 (UTC)
To: supervision@list.skarnet.org
Original-X-From: supervision-return-2118-gcsg-supervision=m.gmane.org@list.skarnet.org Sat Jun 28 21:12:51 2008
Return-path: <supervision-return-2118-gcsg-supervision=m.gmane.org@list.skarnet.org>
Envelope-to: gcsg-supervision@gmane.org
Original-Received: from antah.skarnet.org ([212.85.147.14])
	by lo.gmane.org with smtp (Exim 4.50)
	id 1KCfqs-0001gl-Fp
	for gcsg-supervision@gmane.org; Sat, 28 Jun 2008 21:12:50 +0200
Original-Received: (qmail 12683 invoked by uid 76); 28 Jun 2008 19:12:17 -0000
Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm
List-Post: <mailto:supervision@list.skarnet.org>
List-Help: <mailto:supervision-help@list.skarnet.org>
List-Unsubscribe: <mailto:supervision-unsubscribe@list.skarnet.org>
List-Subscribe: <mailto:supervision-subscribe@list.skarnet.org>
List-Archive: <http://www.skarnet.org/lists/>
Original-Received: (qmail 12673 invoked from network); 28 Jun 2008 19:12:17 -0000
X-Injected-Via-Gmane: http://gmane.org/
Original-Lines: 52
Original-X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 209.59.210.144
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/21.4 (gnu/linux)
Cancel-Lock: sha1:nDGE1H46Jo1II6tN6p0lvAH6A2M=
Cache-Post-Path: purity-of-essence.net!unknown@216.27.138.10
X-Cache: nntpcache 3.0.2 (see http://www.nntpcache.com/)
Original-Sender: news <news@ger.gmane.org>
Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1883
Archived-At: <http://permalink.gmane.org/gmane.comp.sysutils.supervision.general/1883>

I've been using runit for a while, and whenever I upgrade to a new
version, I want to shut down everything and then restart, so that I can
make use of the the newest runsvdir and runsv binaries.

However, when I have done this, I have found that I often find problems
with the existing lock files and sockets that runsv uses.  Therefore,
I've come up with a procedure for doing a complete restart that deletes
these files as part of the process.

My procedure seems like overkill, however, and I'm hoping that there is
some lack of understanding that I have which, when corrected, will
result in my knowing how to do this in a more straightforward manner,
and without any manual file deletions.

Here are my steps. Can any of you could suggest improvements? Thanks in
advance.

  # cd /service
  # for i in *
  > do
  > sv stop $i
  > done

  # vi /etc/inittab   # (I'm using sysvinit and inittab)
  ... comment out this line, save the file, and then exit from vi:
  SV:123456:respawn:/sbin/runsvdir-start

  # init q

  # pkill -f runsv 

  # cd /etc/sv
  # find . -name ok | xargs rm
  # find . -name lock | xargs rm
  # find . -name control | xargs rm

  Now, do the complete runit upgrade.

  Then ...

  # vi /etc/inittab
  ... un-comment the line that I commented out above,
  ... save the file, and then exit from vi

  # init q



-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.