Apologies to wingmen on my older Xeon/CUDA server. In a fit of heat- or svn-frustration-induced fever today I typed the fateful command 'rm -rf *' thinking that I was connected to another computer in another window in another workspace and not in my $HOME directory. :-( By the time I realised that the command was taking longer than it should, and hit Ctrl-C, I'd lost all files (alphabetically) down to boinc* -- which included BOINC, so all my WUs are lost.

Sorry.

boinc_repository was still intact, so I've rebuilt the boinc executables, and the CUDA executable is still in its build directory; so I just need to recreate the app scripts. Now we're up again after maintenance I'll try to reattach, merge with the old instance, and abort/reset so the WUs can go to new homes. I can't actually crunch on the machine at present, the server-room A/C failed yesterday so I shut down all S@H jobs so we can do our "work" work without reaching harmful temperatures.

[Edit] Ah, it looks like the server automagically merged the new instance and abandoned all the pending tasks. Now to wait for the A/C to be repaired before starting again. [/Edit]

---

How blue was the air in your room, at the time you found out? ;-)

---

How blue was the sky today, at 30.4 C outside (and just a few tenths less in my office...)?

---

I can't actually crunch on the machine at present, the server-room A/C failed yesterday so I shut down all S@H jobs so we can do our "work" work without reaching harmful temperatures.

I met a service tech in the lift on my way out tonight -- he'd just replaced the faulty thermistor in the A/C unit, so I'll see if I can start bringing up background S@H jobs on all the servers again tomorrow (I have been running just on one that's designated as my "personal" development machine), without overloading the system. My RAC is starting to take a beating...

---

I can't actually crunch on the machine at present, the server-room A/C failed yesterday so I shut down all S@H jobs so we can do our "work" work without reaching harmful temperatures.

I met a service tech in the lift on my way out tonight -- he'd just replaced the faulty thermistor in the A/C unit, so I'll see if I can start bringing up background S@H jobs on all the servers again tomorrow (I have been running just on one that's designated as my "personal" development machine), without overloading the system. My RAC is starting to take a beating...

It's fine. There is no rush. It leaves a bit of work for the rest of us. :)

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

It's fine. There is no rush. It leaves a bit of work for the rest of us. :)

Cheers, mate, shall I leave it until Monday then?

---

It's fine. There is no rush. It leaves a bit of work for the rest of us. :)

Cheers, mate, shall I leave it until Monday then?

Either is fine for me. I left work for the holiday weekend & forgot to flip a few machines on myself.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

...In a fit of heat- or svn-frustration-induced fever today I typed the fateful command 'rm -rf *' thinking that I was connected to another computer in another window in another workspace and not in my $HOME directory. :-( By the time I realised that the command was taking longer than it should, and hit Ctrl-C...

Ivan, my friend, you are not the first to do that and I doubt very much you will be the last. I have done the same. On a client's server... Unsurprisingly, that one very nearly cost me my job.

No matter how experienced you get and how much you you think you know, the universe knows more and will sideswipe you with the tiniest of reasons :)

At least it's all easy enough to get back up and running again, if a bit time consuming.

---

~W