On Tue, Feb 04, 2003 at 11:38:52PM -0600, Stephen M. Jones wrote:
> This was reported in 1.5.3 and apparently hasn't been
> fixed in 1.5.4 released on Feb 1st. Does anyone have
> a patch for this?
It will not be fixed on the 1.5 branch. Please upgrade to 1.6.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>