On Wed, 9 Mar 2011, Michael Eager wrote: > The problem with randomly replacing various components, other than > the downtime and nuisance, is that there's no way to know that the > change actually fixed any problem. When the base rate is one > unknown system hang every few weeks, how many wees should I wait > without a failure to conclude that the replaced component was the > cause? A failure which happens infrequently isn't really amenable > to a random diagnostic approach. So you pitch the whole thing over to being a test rig, and buy all new hardware? jh