[quote=Anonymous;126402]We're doing port 100 (lower range) only. We were discussing doing it on both servers, but Carlos wanted to get the port 100 server cleaned out and closed up (all those servers use a bit too much RAM on his machine), so we decided to do it on port 100.

As for splitting it off into another thread, I suppose we could do that. What does everyone else think?[/quote]
Thanks for clearing that up. Erm...why in the post below that you say tomorrow, if it's 7 PM GMT Sat? Or is it not 7 PM GMT Sat?
When is it, again?

[quote=Anonymous;126403]Maybe it's just some people who want to do a "last blast" on the port 300 server before they switch to the port 100 server for the rally. :wink:

Don't worry, I'm sure we'll see everyone on the port 100 server by tomorrow afternoon. :smile: (I can't imagine anyone minding the fact that it's working on the lower range; remember, most of the first rally was done with the port 300 server still on the lower range, and nobody seemed to mind that.)[/quote]

I'm one of those people. All machines are on port 300 until Friday afternoon. Then they'll be on port 100 all weekend; almost 3 days. I don't plan to run in to work to change anything. My connected home machines will be sieving, running port 100 for the rally, and then back to sieving afterword. I'll then divide up the work machines starting next Monday; about half on port 100 and half on 300.

So everyone for the rally, if you're currently running port 300, make sure you clean out your worktodo.txt queue using Anon's instructions above. (You cannot submit port 300 k/n pairs to port 100. It will reject them I believe.) After cleaning your queue, all you need to do is change the port in your llr-clientconfig.txt file from 300 to 100.

It's all good Carlos. No worries. :smile:


Gary

[quote=Mini-Geek;126405]Thanks for clearing that up. Erm...why in the post below that you say tomorrow, if it's 7 PM GMT Sat? Or is it not 7 PM GMT Sat?
When is it, again?[/quote]

7 PM GMT Saturday is the correct starting time. But I will be changing my machines over by late Friday afternoon here (late evening GMT). Others especially in the U.S. may do the same if they don't want to be messing with their machines on Sat. morning before the rally.


Gary

I have added so far one quad-core 2.95 GHz and three P4 3.0 GHz.
Beyond will move all his cores later this evening to the party...lol
I hope to see more people running LLRnet on server port 100. Since last start up of the servers, the server on port 300 received 54217 results and server on port 100 29407 results, let's change this ratio shall we?

Carlos

[quote=em99010pepe;126492]I have added so far one quad-core 2.95 GHz and three P4 3.0 GHz.
Beyond will move all his cores later this evening to the party...lol
I hope to see more people running LLRnet on server port 100. Since last start up of the servers, the server on port 300 received 54217 results and server on port 100 29407 results, let's change this ratio shall we?

Carlos[/quote]
I've currently got one core of my Core 2 Duo 2.2Ghz on port 100, and the other on port 300...going to change the second core over to port 100 right now. :smile:

When an llrnet server is configured as a proxy, is the "proxyName" or individual client "username" returned to the "proxyMaster"?

[quote=AES;126502]When an llrnet server is configured as a proxy, is the "proxyName" or individual client "username" returned to the "proxyMaster"?[/quote]

Tnerual?

Carlos

Carlos, do you see results from AES_CLIENT or AES_PROXY on the port 100 server?

[quote=AES;126506]Carlos, do you see results from AES_CLIENT or AES_PROXY on the port 100 server?[/quote]

I see AES_PROXY.

[quote=em99010pepe;126508]I see AES_PROXY.[/quote]

Thanks Carlos. There's the answer.

That means a team called AES with a member called PROXY...lol
I'll return within 5 hours. Bye.