Automated primality testing with LLRnet for CRUS

[Beyond]

Beyond,

I'm less than 12 hours to move the rest of my fleet to server port 100. So far I have 3/8 on it. Care to join me for a week? I'll stay there until I dry out the server.

Carlos

I'll join you tomorrow.

On the job front, I have it on good authority (the owner) that the office closings are not scheduled till next month and I personnaly have no worries, my job is secure.

The only good thing about this mess, is I will have access to those other 2 offices machines when we move them to our office for storage. I have a "good" place picked out for storage (in my office).

[IronBits]

[Beyond]

I was sweating bullets for a while .... too old to start over now.

[em99010pepe]

I'll join you tomorrow.

I'm already there with 7 cores, more to add.

Carlos

[Beyond]

I've added 5 of the 8 machines in my office at work. I'll start moving the home machines to port 100 when I get home in a couple of hours.

[em99010pepe]

IronBits, are you going to move the rest of your cores to server port 100?

[Beyond]

Carlos, I think your server has crashed ...... several people are unable to connect.

[IronBits]

IronBits, are you going to move the rest of your cores to server port 100?

Yes, shortly. Have to empty the cache first, then switch the port...

[Beyond]

Yes, shortly. Have to empty the cache first, then switch the port...

I'd wait to see if the server recovers, port 300 server is still running, but port 100 is down.

[IronBits]

LLRnet-CRUS current status :
Sleeping ...
LLR network client 0.9b7 started
Based on LLR version 3.5.0
Loading library 'win32' ...
winloop thread
LLRMain started
server dialog thread started ...

I guess that's what you mean