View Single Post
Old 2008-01-25, 18:30   #2
mdettweiler
A Sunny Moo
 
mdettweiler's Avatar
 
Aug 2007
USA (GMT-5)

3×2,083 Posts
Default LLRnet server FAQ

Q: Is there a deadline for returning LLRnet results?
A: Yes. Currently the deadline is 7 days from the time when the number was handed out to your client. After 7 days, if you still haven't finished crunching your number (or simply haven't been able to return it yet even if it is finished), it will be assigned to another person.

Q: Can I cancel a number that I don't actually want to crunch for whatever reason, or is over deadline?
A: Yes. Simply open up a command prompt (on Windows it's Start>Run, then type "cmd" and press Enter), navigate to the LLRnet folder (by typing the "cd" command, such as: "cd c:\llrnet"), and type the command "llrnet -c" and press Enter. LLRnet will start, cancel the current number, and close. (Your command window will still be left open.) Note that if you have a cache size greater than 1 (the default is 10), then you'll have to enter that command again for each additional number in the cache that you want to cancel. (LLRnet will say "no numbers left to cancel" if you've canceled them all and you execute the command again.)

Q: Can I run LLRnet on a multi-core system and still utilize all the cores?
Yes, though LLRnet by default can only utilize one core. Thus, you'll have to run multiple copies of LLRnet. Simply, when installing, extract the archive you downloaded into as many folders as you have cores (such as c:\llrnet, c:\llrnet2, etc.). Then, configure the llr-clientconfig.txt for each core (you have to configure each installation separately--and if you're using the stock version, make sure to change the GUIPort value to something different on everything except the first installation. You'll also have to change this value in the llr-guiconfig.txt for the installations that have been set to a different GUIPort.), and run the llrnet.exe (or "llrnet" on Linux/FreeBSD) in each installation. You'll see as many LLRnet icons in your system tray as you have cores--you can control each core's LLRnet separately. (You can also configure one core's GUI, if you're using the stock LLRnet, to control all the other cores, too, though that's a little bit more of an advanced topic--you can either try to figure it out on your own, or just post here begging for help. )

Q: Can I switch an LLRnet installation from the Sierpinski server to the Riesel server, or vice versa?
A: Sort of. You can't just go and change the "port" at a whim; then, any results currently in queue or being crunched will be erroneously returned to the wrong server, and thus rejected, while meanwhile they just sit around on the "real" server until they go past deadline. Thus, you need to clean out your LLRnet client's queue before you switch servers. Yes, you can do this by canceling all numbers that you have in queue, but that's less than optimal--you'll end up wasting some of your work, as well as leaving a mess on the server side for Carlos to have to clean up. Here's how to clean out the client the correct way:
-Close the LLRnet client.
-Open up llr-clientconfig.txt, and scroll down to where it says "WUCacheSize = x". Change x to 1, then save the file and start LLRnet again.
-Let LLRnet run until it's done as many k/n pairs as your queue was set to previously. Check the "workfile.txt" file in the LLRnet folder to verify that there's only one k/n pair left. (Note: the first line is just a header, it doesn't count--so if there's two lines in the file, there's one k/n pair in queue.) If so, then close out LLRnet, and open up llr-clientconfig.txt. Find the line that says "--once = 1" and remove the -- marks. It should just say "once = 1". Save the file, and open up LLRnet. It will work on the current k/n pair, return it to the server, and exit--rather than downloading another pair from the server.
-After LLRnet has exited, open up llr-clientconfig.txt again, set "once = 1" to "--once = 1" again, set "WUCacheSize" to whatever you'd like it to be (probably whatever it was before), and change the "port" value to the one for a different server. Save the file and start LLRnet.
-You've now successfully transferred LLRnet to the other server, with no loss of work whatsoever!


Q: I'm not constantly connected to the Internet. Can I set LLRnet to keep a larger queue to last until the next connect?
A: Yes. Simply close out LLRnet, open up llr-clientconfig.txt, set the "WUCacheSize" value to however many workunits you want to keep in queue, and restart LLRnet. The maximum is 100, though that should be more than plenty even for the small numbers we're doing right now.

If you have any more questions that should be added to this list, please post here.

Last fiddled with by mdettweiler on 2008-01-26 at 00:25
mdettweiler is offline   Reply With Quote