On Mon, 2007-21-05 at 00:04 +0000, Johnny Blonde wrote: > > > On 21 Mai, 00:30, "Noah Gift" <[EMAIL PROTECTED]> wrote: > > As a sysadmin for many years I say not likely. More than likely it is > > a hardware problem such as bad RAM. Applications that tax a machine > > will find a weak point in the hardware. It is also less likely that > > the OS may have something wrong with it, but looking at the logs > > files should tell you very quickly. > > That´s the most strange thing about it: there´s not a single hint in > the logs - not even a single error-message, nothing. the log just ends > when the crash happens, without anything. > > > > > Anything is possible, but when I hear a busy application crashes a > > machine...I think bad RAM. I have seen it many, many times. > > > > this is something the vendor told us, too. i then ran some RAM-tests > on the machine, without result. > Maybe i have to try them again.
Do some research on RAM tests. Many just don't work well. I have been told ( but am now expert ) that heavy compilation is often an even better test. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
