On May 27, 2011, at 6:47 PM, Leif Hedstrom wrote: > On 05/27/2011 11:43 AM, Leif Hedstrom wrote: >> Hi all, >> >> I've prepared a package for a v2.1.9 release. Please take a look at the >> artifacts, check the STATUS/README/CHANGES files, and do builds and tests. >> After finishing your examination of the release candidate, please cast your >> ±/0 votes, I will call the vote on 5/30/2011. The src tar-ball and >> signatures are available in >> >> http://people.apache.org/~zwoop/rel-candidates/ >> >> >> The relevant files are >> >> trafficserver-2.1.9-unstable.tar.bz2 >> trafficserver-2.1.9-unstable.tar.bz2.asc >> trafficserver-2.1.9-unstable.tar.bz2.md5 >> trafficserver-2.1.9-unstable.tar.bz2.sha1 >> > > Also, when testing this, it's highly recommend that you blow away all cache > files, and use the latest records.config file (with your own modifications). > We've done a fair amount of changes to various caches as well as settings. At > a minimum, I'd recommend > > % sudo rm etc/trafficserver/internal/hostdb.config var/trafficserver/* > % sudo bin/traffic_server -Cclear > % sudo rm var/trafficserver/server.lock > > > after you've upgraded and put new records.config in place. This should > hopefully not be necessary when upgrading from v2.1.9 to v3.0.0, since we're > not planning any more incompatible changes. >
That clears up some issues I saw. +1