:: 15-Jan-1999 12:40 (Friday) ::
Build 303 of the personal proxy should begin to become available for
the regular platforms soon. This new build addresses a few issues
that users have been bringing to my attention. Specifically, the few
that I can recall off the top of my head are:
– temporarily disabled logcompressor until buffer corruption can be
completely resolved.
– buffers will autorepair when validation fails.
– updated documentation and sample ini files to more closely reflect
available options and command line arguments
– proxy no longer attempts to window as many block requests if the
additional needed number is low.
– pidfile now contains correct pid when -detach is used.
– much major internal reworking of DES handling code that was being
developed in a separate CVS branch to accommodate EFF macrospace
distribution has been merged into the main proxy code.
– block alignment issue addressed to ensure that blocks crossing the
boundary are not distributed.
– cumulative block totals have been added to the end of the contest
status lines that are periodically printed (“tot=xxx”)
– the contest status lines are now printed every 30 seconds by
default, but this should now be adjustable via the ini file option
[misc]/statusperiod
– additional logic to allow the proxy to intelligently discard DES
blocks from non-active contests added.
It is believed that the execution of the logcompressor may have been
contributing to the corruption of buffers, however we are still trying
to test this hypothesis, since it does not seem completely definite.
Until the issue can be resolved, automatic log compression has been
disabled, but log rotation should still occur. Regardless, buffers
should automatically repair when the proxy detects the condition to be
severe enough.
Unfortunately, I will be out of town all this weekend through Monday
evening, which means that I will not be present for the start of the
contest. I will instead be enjoying my 21st birthday snow-boarding on
the slopes. However, I have confidence that my cow-orkers at
distributed.net can handle the contest start smoothly.
Although I believe this build to be much improved over the original
build 300, I continue to urge users who are still running a build 280
and are not comfortable running code that is still under development
and testing are encouraged to continue running their build 280 until
all issues are resolved.
However, if you have already taken the leap to the build 300 series,
you are highly recommended to upgrade to this latest version when your
platform’s build becomes available.
Thanks again for your support! Please continue to look for problems
and send them to me as you find them.