Could this problem be kernel related, and if so is it fixed in the actual
2.0.33 release? If not, is it on the 2.0.34 fix-list?
Or should I just blame increasing system load?
-- Thanks in advance, Bjarni R. Einarssonbre@margmidlun.is [ THIS SPACE INTENTIONALLY LEFT BLANK ] http://www.mmedia.is/~bre Juggler@IRC "Your revolution is a silly idea, yeah." - REM