Automated primality testing with LLRnet for CRUS

[alpha]

Restarted the client and it is working again now.

Cache size is just the default of 10. Doesn't really matter because I'm running it alongside dnet. For most of the time I've contributed to this it has only been half a core but I gave it a full core overnight last night.

[em99010pepe]

Restarted the client and it is working again now.

Cache size is just the default of 10. Doesn't really matter because I'm running it alongside dnet. For most of the time I've contributed to this it has only been half a core but I gave it a full core overnight last night.

Ok. Got 5 results from you.

[em99010pepe]

Ironbits,

Please check all your cores running on server port 100. Last contact before the server went down was from one of your machines. A few years ago RieselSieve had a similar problem and it was a faulty client that jammed the server.

Thank you.

Carlos

[em99010pepe]

Beyond,

I'm pulling off my machines from LLRnet and feed them with manual work from the lower ranges. I reserved a range that will put my cores busy for two weeks.

Carlos

[Beyond]

I have not geared up yet and you are pullng boxes off?

[em99010pepe]

I have not geared up yet and you are pullng boxes off?

I'll do the work not with LLRnet client but with LLR standard client.

[em99010pepe]

I changed one of the server settings allowing more number of concurrent connections. The server port 100 had 8 and server port 300 had 16, changed both to 30. Let's see what happens.