I may have spoken too soon yesterday, when I said that top(1) was still
leaking memory. I left it overnight, and it's not hogging resources like it
used to:

  PID USERNAME PRI NICE   SIZE   RES STATE   TIME   WCPU    CPU COMMAND
 8577 mason     28    0   384K  464K run     8:17  1.30%  1.30% top

In the past, with 3.5b5, if I left it overnight, it would be using a meg or
a meg and a half of memory when I checked in the morning. The current
behaviour is much more reasonable. Memory usage appears to wobble around a
bit, but it doesn't steadily increase like it did in the past.

ObSelfDeprecation:
Wolf! Wolf! <slap> Oh. Sorry.

--
Mason Loring Bliss...mason@acheron.middleboro.ma.us...www.webtrek.com/mason
"In the drowsy dark cave of the mind dreams build their nest with fragments
 dropped from day's caravan."--Rabindranath Tagore...awake ? sleep : dream;