Recommended steps for upgrading?

[Lloyd Zusman <ljz@asfast.com>]

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.