On Fri, 20 Apr 2007, Quanah Gibson-Mount wrote:
I tested and verified that this error has been fixed since the 2.3.32 release. If you upgrade, you should not encounter this problem in the future.
Thanks, Quanah; I'll look at upgrading on the morrow.