Antiweb 4.0BETA15

[do...@hcsw.org]

Upgrading to this Antiweb release requires stopping and restarting the
hub process. You will also need to recreate the hub directory. Sorry for
any inconvenience. Believe me we aren't thrilled with this either:

# antiweb -stats /var/aw

"--------ANTIWEB HUB STATS---------
Hub dir: /var/aw
Hub uptime: 243d 11h 34m 17s
...

:)

Also check out the cool new processes diagram on the homepage:

http://hoytech.com/antiweb/

---------------------------------------------------------------------
We have just released 4.0BETA15:

git: commit be047162e35d0be4c2c7394b87c77a3e987fd329

tarball: http://hoytech.com/antiweb/beta/antiweb-4.0BETA15.tar.gz
CKSUM: 1636283518 220492
MD5: 59a556061106dcaf856f789d0c06834a
SHA1: c456797b458d7df92c459631227eb3e3b3b3deb4
---------------------------------------------------------------------
4.0BETA15 Sep 12, 2009

* Bugfix: Don't allow already registered worker connection to
register another worker connection.
* Bugfix: Uses volatile sig_atomic_t for variables set inside
signal handlers (currently just time_for_a_reaping).
* Bugfix: Improved confusing log message when a worker requires a
worker cache but none is present.
* Bugfix: Support closures in install-hub-rewrite-host.
* Bugfix: SO_REUSEADDR wasn't being set properly so sometimes the
hub wouldn't restart until you waited for sockets to timeout.
* Change: Logging is now done by a separate logger process
which is connected to the hub. This is so that the hub process
never has to do blocking disk I/O. Furthermore, a compromised
hub process can no longer access previously created log files
because it is now chroot()ed to an empty directory.
* Change: git is now used for version control, not CVS.
* Feature: New warning flags variable for controlling warning
flags passed to gcc when compiling libantiweb.c.
---------------------------------------------------------------------