Re: Recommended steps for upgrading?

[Lloyd Zusman <ljz@asfast.com>]

"Radek Podgorny" <radek@podgorny.cz> writes:

>> Lloyd Zusman <ljz@asfast.com> writes:
>>
>>> [ ... ]
>>>
>>> Here are my steps. Can any of you could suggest improvements? Thanks in
>>> advance.
>>
>> I'm sorry for responding to my own message, but I left a step out of my
>> procedure. Here's the corrected version:
>>
>>   # cd /service
>>   # for i in *
>>   > do
>>   > sv stop $i
>>   > done
>
> "sv st /service/*" works for me so "sv stop" should work, too IMHO...

Thanks. I'll do "sv st{op} /service/*" next time.

If you folks agree that there isn't any way to avoid the manual kills of
the runsv and svlogd processes and the manual removals of the sockets
and the lock files, what do all of you think about having this
documented somewhere in the "upgrading from previous versions" page
(http://smarden.org/runit/upgrade.html)?  I'd be happy to submit an
attempt at this documentation.

I've gotten bit more than once with this during upgrades, where the
runit-based processes wouldn't properly restart, and I wouldn't doubt
that others might have encountered similar difficulties.


>>   # 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
>>   # pkill -f svlogd  # (this is the step I left out)
>>
>>   # 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.