On Tue, 2002-01-08 at 11:45, xOr wrote: > Has this problem gone away in any releases since 0.61.2pre4?
Unfortunately, the last version I tried for a prolonged period thus far still exhibited it at least once that I caught, and that was version 0.62.0pre0. I've since upgraded that box to 0.62.0pre2 and have been monitoring it. Jamin W. Collins
