Posts by Steven Douglas Huddleston

1) Questions and Answers : Wish list : Everybody's Wish (fer-sure!) (Message 159684)
Posted 30 Aug 2005 by Profile Steven Douglas Huddleston
Post:
You should post that over on the Boinc forums, you know. :)


Now why didn't I think of that? (It must be my grief-stricken state.)

The deed is done! Thanks for the "wake-up-slap".
2) Questions and Answers : Wish list : Everybody's Wish (fer-sure!) (Message 159645)
Posted 30 Aug 2005 by Profile Steven Douglas Huddleston
Post:
Mostly people combine their OS crash with Boinc is shit.. It's good to read the other side of the story once. :)


Ahh...yes! Well, most people today are too young to remember an age where "instant gratification" was not in the lexicon. I'm a career coder, so I know what the poor guys at SETI & BOINC must be going through.

A backup option for the client_state.xml, now there's a good one. I'll be asking for this as well. Although I am not quite sure how they would implement this prior to a crash, since crashes never make themselves known. ;)


There is an even better idea! Let's get a discussion started on this, see what ideas may pop up. Who knows what un-harnessed resources are waiting to be tapped in that most-ignored-of-the-distributed-computing-peripherals: The User!

Although the client_state.xml file does make a backup of itself... each time it is being written to: Client_state_prev.xml


Practically useless, unless you discover something is terribly wrong and stop everything before BOINC restarts (and makes a new copy of the already modified client_state). This is like the "last known good configuration" in Windows. If you realize something went wrong before you log on, then you are saved. The problem is you don't usually know something is wrong until after you log on.

...for you to not auto start Boinc on startup (difficult as hell when it's a service), and first check if the prev file is still there, then rename or copy that one to the client_state.xml file. And only then start up Boinc.


Hmmm...how about this: Why delete finished work units at all during a reset? Why not just reset the units in progress, (and whatever is left in the queue if you like), but leave the finished work intact.

As for a backup strategy, I suppose it should not be too hard to program an extra feature into the configuration that backs-up all the critical files in a backup directory, (say, "C:/.../BOINC/BACKUP"), at a user configurable interval, (every 10 minutes, every 1 hour, whatever!), a "RESET" can then just return to that backup-state and at least all would not be lost. Two redundant backup file sets would eliminate the problem altogether since any reboots that happen during the backup-write process would leave the second set intact. If your interval is set to "every one hour" then the most you'd lose in the worst case scenario is two hours of work!!!

I suppose this is one update that would be greatly appreciated, I think, (Returning to your comment on user-judgments), by all but the most hard-core, die-hard misanthropes out there.

Wouldn't that help to reduce the "BOINC-flame-queues" considerably? I betcha that's bogging down the servers some. :D
3) Questions and Answers : Wish list : Everybody's Wish (fer-sure!) (Message 159388)
Posted 29 Aug 2005 by Profile Steven Douglas Huddleston
Post:
What did reset? Did you reset the Seti project yourself? If you did, why did you do that?


You know? I have no idea! No, I most certainly *DID NOT* reset it.

No, Ageless, I know better than that.

I was browsing something or other (not SETI related) and the browser got locked up, (!@#& Microsoft!), I had to reboot the non-responsive system. If you look at the snippet of log I posted you can see it's from the startup. I think BOINC wasn´t able to close its files properly before the reboot, which is strange because it was a task manager shutdown.

(Sigh!) Oh-gwey, Cest la vie!
4) Questions and Answers : Wish list : Everybody's Wish (fer-sure!) (Message 159370)
Posted 29 Aug 2005 by Profile Steven Douglas Huddleston
Post:


Steven,

Apparently you imagine yourself in a market , being about

bargaining a great deal or gaining the prize of a lottery or winning

the big lot and at the end of year calculating the rate of your benefits

or your losses .


??? I have no idea what you are talking about. I thought this was the "Wish List" So, I made "a wish".

Here is a week's worth of good work done for a really cool cause, gone to waste due to a freaky software quirk.

I think you have mistaken my meaning, (which is common with polyglots), I'm not competing with anyone, it's just the waste of energy (effort) that I find appalling. Some of us are really interested in the science of it, and try our best to be as efficient as possible.

This problem can easily be eliminated by coding into the software a backup procedure for whenever the software is going to reset. How can losing properly processed work units be good for the project? Isn't the idea of distributed computting all about doing more work in less time?

It hurts when our good-hearted efforts vanish for *no good reason*.
5) Message boards : Number crunching : Send results after resetting project (Message 158967)
Posted 29 Aug 2005 by Profile Steven Douglas Huddleston
Post:
It won't be the first time I've done surgery on a file!

Can you tell us how to go about it?

I can probably write an app to do this for everyone if I knew where to get the information needed to rebuild the client_state.xml file.

I've looked, it's not in the results file, unless some heavy conversion is required, but then I'd need to know what the rules are.

Can you elaborate on that?

Anyone?

6) Questions and Answers : Wish list : Everybody's Wish (fer-sure!) (Message 158958)
Posted 29 Aug 2005 by Profile Steven Douglas Huddleston
Post:
Oh how nice it would be to have a cute little button you can click on and have all of your completed Work Units restored to the client_state.xml file after a reset! After all the work is there in the project directory, each with its associated result file. Losing all of that time because of some BOINC freak-out seems just plain evil to me.

Isn't there a clever coder out there who can make this right?

Here's what happened:

StartServiceCtrlDispatcher being called.
This may take several seconds. Please wait.
2005-08-28 09:27:45 [---] Starting BOINC client version 4.45 for windows_intelx86
2005-08-28 09:27:45 [---] Executing as a daemon
2005-08-28 09:27:45 [---] Data directory: C:Program FilesBOINC
2005-08-28 09:27:45 [---] BOINC is running as a service and as a non-system user.
2005-08-28 09:27:45 [---] No application graphics will be available.
2005-08-28 09:27:45 [---] Can't parse file info in state file
2005-08-28 09:27:45 [---] State file has different major version (0.00); resetting projects
2005-08-28 09:27:45 [SETI@home] Resetting project
2005-08-28 09:27:45 [---] request_reschedule_cpus: exit_tasks
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found
2005-08-28 09:27:45 [SETI@home] PERS_FILE_XFER_SET::remove(): not found

...etc...

The work of a whole week (on a p4 HT going at 3.00 GHz, 2 CPUs), gone in an instant!

(Sob!) Boo hoo hooooooo!





 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.