runit - upgrading from previous versions

0.13.0 or 0.13.1 to 1.0.x

No further action from you is required.

0.12.0 or 0.12.1 to 0.13.0 or 0.13.1

runit's service logging daemon svlogd now can be configured to transmit selected log messages through UDP. For reliable network logging through TCP with support for authentication, authorization, and encryption, and also on how to use the new feature to configure syslog compatible remote UDP system logging, see the socklog package.

0.11.x to 0.12.0 or 0.12.1

With this version runit supports running under sysvinit on the Solaris platform. Replacing init on Solaris is not yet supported. The services directory now defaults to /var/service/ instead of /service/.

0.10.0 to 0.11.0 or 0.11.1 or 0.11.2

This version introduces the new chpst program, which changes the process state as specified by command line options, and runs another program with this process state.

0.9.x to 0.10.0

No further action from you is required.

0.8.0 or 0.8.1 to 0.9.x

The svlogd program is new. svlogd is a service logging daemon designed to be run from log/run files, similar to multilog. The runsvdir program no longer propagates the TERM signal to the runsv processes if it receives one, but exits immediately, and runsvdir now supports handling of the HANGUP signal, see the man page for details. svwaitdown has changed to additionally send the down command to the services it works on, if not yet done.

0.7.x to 0.8.0 or 0.8.1

With this version runit's handling of its magic files has changed slightly for better support of read-only root filesystems. You should adapt stages 1 and 3 and ctrlaltdel to set file permissions on the magic files instead of creating and removing them; please take a look at the examples in /package/admin/runit/etc/.

The runit program now calls the reboot() function if possible, and if stage 3 didn't take care of this.

0.6.0 to 0.7.0 or 0.7.1 or 0.7.2

This version introduces runlevel support with the new runsvchdir program. See the runlevels documentation for more information.

The runsvdir and runsv programs have changed and should be restarted. If you want to switch runlevels, runsvdir must be restarted. This is done on the next reboot or by following these steps:

 # cd /service
 # for i in *; do if test "$i" != getty-5; then svc -d $i; fi; done

Check for the services being down:
```
 # svstat /service/*
```
If all services other than the getty-5 service are down, kill runsvdir by sending it a HUP signal:
```
 # kill -HUP <pid_of_runsvdir>
```
Replace <pid_of_runsvdir> with the pid of runsvdir. The runit program starts the new runsvdir program now, which starts the new runsv processes.

0.5.0 to 0.6.0

There are two new programs, runsvdir and runsv, which replace the svscanboot/svscan/readproctitle/supervise combination of daemontools. Please adapt runit's stage 2 (/etc/runit/2) to use runsvdir instead of svscanboot; see the examples in /package/admin/runit/etc/. The change takes effect on the next reboot or if you stop all services and kill svscan and readproctitle. runit then automatically restarts stage 2.

The svwaitdown program has new options: -k and -x. They are used in runit's stage 3 (/etc/runit/3). Please adapt your /etc/runit/3 script after the changes to stage 2 have taken effect (runsvdir must run instead of svscanboot); see the examples in /package/admin/runit/etc/.

0.4.1 to 0.5.0

There is a new program: utmpset. This program is used in the getty run scripts to enable local login accounting. You might want to adapt your getty run scripts /service/getty-*/run, see the examples in /package/admin/runit/etc/.

Gerrit Pape <pape@smarden.org>

$Id: upgrade.html,v 1.30 2004/07/28 15:58:22 pape Exp $