I'll gather my log files too, when current work units are done. Kills me to think of the wasted clock cycles.
I'll gather my log files too, when current work units are done. Kills me to think of the wasted clock cycles.
Wow.
Fourteen years of work gone in an instant.
What an extreme example of the need for OFF SITE BACKUPS.
Can the wayback machine possibly help to get some of the code back?
I'll allow my current assignments to finish. What are you wanting when they're done? My results.txt file? Something else?
Regardless, I'll find some other diversion for my OCD.
This is just too painful of a mind**** to process at the moment...
I did miss that somehow. Thanks for bringing it up again.
Louie's the one who would be interested in code, so the Wayback machine might possibly be of use to him.
As for off site backups, you've got that right. Stuff happens. I had a 110-story building fall on top of one of my data centers once, Not only did we not lose data, but our business operations didn't miss a beat. Both Jim and myself are rather obsessive about making sure the data is backed up, including daily copies to an off-site location. In the event of a real disaster, PrimeGrid may be down for as much as 24 hours, but at worst we'll lose the last day's results. If you do this stuff long enough, you see this kind of thing happen over and over. If you do it for a living, you're expected to make sure that you're protected against this kind of event because it's a matter of when, not if. The problem is that when you're running things on a shoestring budget that's typical of an operation run as a hobby or a club, it can be really hard to put together the resources just to keep the operation running, let alone to have adequate assets in place to handle disaster recovery scenarios. So let's not judge the powers that be too harshly because it's difficult enough just to keep something like this running.
For me personally, I use a backup system that lets me back up my entire family's computers to the cloud.
As for which files, what I'm interested in is anything that lists test results, meaning the number being tested and the residue produced by the program. I have no idea what Louie might want.
Finally, yes, this is a huge blow. No way to sugarcoat this; it's going to set back this search quite a lot if the data can't be recovered. The only good news in this is that because we decided to split the project between SoB and PG by k's, at least we have all the data for 2 of the 6 remaining k's. Only two thirds of the work is lost rather than all of it.
I'm not judging anyone.
It was simply a statement alluding to my shock and sorrow regarding all the years of work lost.
Hindsight is always 20/20, I know. Lesson learned.
Please DO let Louie know about the Wayback Machine!
It might take a bit of source code browsing but, even with my limited skills, I'm able to get into some of the back-end directory structure, so...
Mike, you never answered my questions.
Would you like me to send you my results.txt file?
Is that the only file you'll need?
Sorry, I wasn't clear! I was stating that MY comments were not intended to be judgemental. I certainly did not mean to imply that you were being judgemental. Everyone's a little shell shocked right now.
Will do.Please DO let Louie know about the Wayback Machine!
It might take a bit of source code browsing but, even with my limited skills, I'm able to get into some of the back-end directory structure, so...
Short answer: Yes! Longer answer: I'm not familiar with SoB's client files, so I don't know. Other people have sent that file, and it seems to have what we would need. That being said, I'd rather have too much information than too little.Mike, you never answered my questions.
Would you like me to send you my results.txt file?
Is that the only file you'll need?
I don't keep all my logs, but I'll see what I have. I was one of the top contributors.