Yes, I am using 2.0.33 and I can say that my system is lightly loaded. Since this only happens on forced check I can live with a reboot once in a while...my previous system was win95 ;)
Thanks > This is common with 2.0.33, is that the kernel version you are using? > Also, just to make folks aware of the situation, I have gotten some really > weird filesystem corruption with 2.0.33 that has (thankfully) always been > corrected by a reboot but I really do not like rebooting these systems as > I do not have physical access to them. I have dropped back to 2.0.32 for > all systems I maintain except the ones I have ready physical access to. > It does not seem to be a problem on the lightly loaded systems, just the > ones that are being pounded rather hard. > BTW, there are constant reports of memory corruption and OOPSies on the > kernel list for 2.0.33 with busy systems. The general rule of thumb is > that unless there is some feature of 2.0.33 that you simply can not live > without, use 2.0.32. -- ---------------------------------------------- Serge Delorme ([EMAIL PROTECTED]) Berthierville, Quebec Canada ABUSUS NON TOLLIT USUM ---------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
