Question about hardware stability: should make really produce the same log each time?
First, rather then explain everything just read this: http://sdb.suse.de/en/sdb/html/hmeyer_memtest-sig11.html That's SuSE page with suggestions for testing your hardware to see if it's good or not (which is what I'm doing). I'm actually running that script now, and _some_ (well, 1) of the log files are _not_ the same size. I'm talking about logs in the middle of the run, not on eaither end. Am I supposed to take that to mean there's something wrong with my hardware? If so, what next? Somehow I can't belive the make should *really* produve exactly the same results each time, but I guess I just don't know. 270 is the bad log file amoung other examples: d572adc3cb360f4bac7cb88f40c378c2 log.260 d572adc3cb360f4bac7cb88f40c378c2 log.261 d572adc3cb360f4bac7cb88f40c378c2 log.262 d572adc3cb360f4bac7cb88f40c378c2 log.263 d572adc3cb360f4bac7cb88f40c378c2 log.264 d572adc3cb360f4bac7cb88f40c378c2 log.265 d572adc3cb360f4bac7cb88f40c378c2 log.266 d572adc3cb360f4bac7cb88f40c378c2 log.267 d572adc3cb360f4bac7cb88f40c378c2 log.268 d572adc3cb360f4bac7cb88f40c378c2 log.269 d572adc3cb360f4bac7cb88f40c378c2 log.27 d41d8cd98f00b204e9800998ecf8427e log.270 d572adc3cb360f4bac7cb88f40c378c2 log.28 d572adc3cb360f4bac7cb88f40c378c2 log.29 d572adc3cb360f4bac7cb88f40c378c2 log.3 d572adc3cb360f4bac7cb88f40c378c2 log.30 d572adc3cb360f4bac7cb88f40c378c2 log.31 d572adc3cb360f4bac7cb88f40c378c2 log.32 -- ---------------------------------------------------- Jonathan Wilson System Administrator Clickpatrol.com Cedar Creek Software http://www.cedarcreeksoftware.com
On Tuesday 07 May 2002 22:52, JW wrote:
270 is the bad log file amoung other examples:
270 is the last one if these logs, 271 hasn't been produced yet, so unless you have more examples I think it's safe to assume that run #270 simply hasn't completed yet when you took this directory listing. Note that the sorting is in alphabetical order, not numerical, so 270 is listed before 28. regards Anders
Hello, AJ >270 is the last one if these logs, 271 hasn't been produced yet, so unless you AJ >have more examples I think it's safe to assume that run #270 simply hasn't AJ >completed yet when you took this directory listing. Sorry, it might be the last of the ones I listed but I'm well over 1000 log files now and that one never got any larger (and I was over 300 when I posted it) Sorry for the confusion. AJ >Note that the sorting is in alphabetical order, not numerical, so 270 is AJ >listed before 28. Yes, I was aware of that Thanks. -- ---------------------------------------------------- Jonathan Wilson System Administrator Clickpatrol.com Cedar Creek Software http://www.cedarcreeksoftware.com
No, I'm double wrong, sorry. You were right that file is now the correct size -- I just got confused. Thanks, sorry. JW >Hello, JW > JW > JW >AJ >270 is the last one if these logs, 271 hasn't been produced yet, so unless you JW >AJ >have more examples I think it's safe to assume that run #270 simply hasn't JW >AJ >completed yet when you took this directory listing. JW > JW >Sorry, it might be the last of the ones I listed but I'm well over 1000 log files now and that one never got any larger (and I was over 300 when I posted it) JW >Sorry for the confusion. JW > JW >AJ >Note that the sorting is in alphabetical order, not numerical, so 270 is JW >AJ >listed before 28. JW > JW >Yes, I was aware of that JW > JW >Thanks. JW > JW >-- JW > JW >---------------------------------------------------- JW >Jonathan Wilson JW >System Administrator JW >Clickpatrol.com JW >Cedar Creek Software http://www.cedarcreeksoftware.com JW > -- ---------------------------------------------------- Jonathan Wilson System Administrator Clickpatrol.com Cedar Creek Software http://www.cedarcreeksoftware.com
participants (2)
-
Anders Johansson
-
JW