|
| ||||
 |
|
Home | Reviews | Tools | Forums | FAQs | Find Service | ISP News | Maps | About |
|
how-to block ads |
2.1 Folding@Home Clients
 got feedback?by nozero Here is a link to an article about someone who didn't get permission. got feedback?by Gizmo Sneakernetting is the ability to transport a work unit from an Internet connected computer to a stand-alone computer for processing and back again to be transmitted!
Note: You will need to change the "asknet=no" in the client.cfg to "asknet=yes"! To be safe, use the -config switch to accomplish it. Please see the updates in the FAH Wiki before trying this ---> Sneakernetting.
got feedback?by Gizmo got feedback?by Gizmo There are two options for this: •asknet=yes This will pop-up a small window asking you if you are ready to connect at the completion of each work unit. In this instance you would connect to the internet via your method, and then tell it OK. This is normally for those that have a connection that has to have a username and password entered before connecting to the internet. •asknet=no This will send and receive work units without any user intervention. Normally for people that are on always-on connections. Note: When using the console version as an installed service, there will be no message box popup. It only prints the message asking to connect to the console window, which you can't see when running as a service, and to the FAHlog.txt file. To install the console version as a service and also use the "Ask before connect" feature, follow these steps: • Go to Start > Run and type services.msc in the box and press the Enter key. • Find the Folding@Home entry in the services listings. Right click (left click if you use a lefty mouse). Then select Properties. • In the Properties window, click on the Log On tab. • Click on the box to the left of Allow service to interact with desktop. • Click the Apply button and then OK. • Restart the client.
got feedback?by MstrBlstr0 The user would have a need to do this if s/he was being particularly careful about the traffic that passes through the system's firewall while s/he was away from it. (Some users like to completely block all traffic on their networks while they sleep.) First you need to be using a rules based firewall. (ZoneLabs free or licensed versions are not rules based to my knowledge.) Some rules based firewalls would include Kerio, Tiny & Sygate. I am using Sygate SPF 5.0 Pro but with a little modification you can take the following instructions and use them on your own rules based firewall. Basically the user will create two rules. One will allow a specific block of IP addresses on a specific port/protocol and the other will block all traffic. Please note that some rules based firewalls read from top to bottom meaning that the rules are implemented in the order they were created. • - Create an advanced rule as you normally would. My first rule is called "F@H." I want to allow both incoming and outgoing traffic from a specific range of IPs on specific remote and local ports so I setup a rule with the following parameters. The IP range that F@H servers uses is 171.64.122.87-171.64.122.144 (Stanford's F@H Server Status Page) The protocol that F@H uses is TCP with a remote port of 80 and a local port of 8080. (Port 8080 is peculiar to the Proxomitron »www.proxomitron.org.) Specify both incoming and outgoing traffic directions. • - Create a second advanced rule to block all IPs on all ports/protocols for all applications. What is nice about Sygate is the user has the ability to enable scheduling which simply means that a specific timeframe can be configured during which time the firewall will block *all* traffic. **Important: Make sure that you place the 1st allow rule on top and the second block all rule immediately below it.**
got feedback?by major marco got feedback?by sortofageek got feedback?by sortofageek Currently there are 6 cores being used. They are Amber, Gromacs, DGromacs, GBGromacs, QMD and Tinker. Info on Amber (core 82) core. Info on Gromacs (cores 78, 79, 7A) core. Info on QMD (core 96) core.
got feedback?by PinHead got feedback?by Spectre93 modes: More Details -config Allows users to change their configuration information. This includes user & team names (reflected in the stats), whether or not to ask before a network connection is made to fetch/send work, set up proxy servers, preferred work unit type (Folding/Genome), process priority, CPU usage requested (5-100%), whether or not to use assembly loops, whether or not to use deadline information, and Machine ID changes. -configonly Same as above, but quit following configuration instead of beginning work. Applicable to client ver. 4.0 only -delete x Delete item #x from work queue. This option should only be used if there is a serious error with the current unit that the client does not automatically recover from (e.g. crash-inducing). This should not normally happen, and if it does, we would be grateful if you could send us the FAHlog.txt file from the unit that causes the error. -license Displays the end-user license agreement Applicable to client ver. 4.0 only -queueinfo Get information on queued work units. Includes for each unit the status (READY/FINISHED/EMPTY), unit type (Folding/Genome), originating server, and date when the unit was received (local time in GMT), as well as deadline if the server sent that information. -send x Send result #x back to server. Exits after trying to send unit (successfully or unsuccessfully). Use "-send all" to send all results outstanding. If unit x is not a completed work unit then the client exits without doing anything. -verbosity x Sets the output level, from 1 to 9 (max). The default is 3. This option should be used if the user wishes to see more detailed client output, particularly useful if there is a problem which needs to be reported to the F@H client development team. -oneunit Instructs the client to quit following the completion of one work unit. Applicable to client ver. 4.0 and up only -forceasm Instructs the core to use SSE/3DNow assembly instructions if possible, even if it has previously made the determination that the machine may not be handling this well. -forceSSE On machines with an AMD processor, Core_78 gives priority to 3DNow over SSE -- this overrides that. Applicable to client ver. 4.0 only Note: As noted by sortofageek  The -forceSSE flag was added to a version 3 client (and version 4 client) due to problems with some AMDs and GROMACs. Since that problem (lockups with some GROMACs WUs) has been resolved by cooperation between AMD and PandeGroup, the -forceSSE switch is no longer needed. It is not recognized starting with the Version 5.00 client.-advmethods The -advmethods flag will allow you to download the latest beta test cores and work units. This also does mean that you agree that if it crashes and causes you grief you won't complain about it, but you will report the issue to Stanford... They want to know. So, it's a little risky but the choice is up to you and you get to test things for Stanford. I only recommend you do this if you have more than one system as things do sometimes go awry. -local Use configuration files from local directory. This option has no meaning on Linux, but is vital on Windows and Macintosh for running multiple clients on a machine. It instructs the client to read its config information from the client.cfg file in the current directory rather than, on Windows, from the installation directory specified in the registry, or, on Macintosh, the Library/Folding@home directory. Information such as the user name, team name, proxy information, machine ID are maintained in the client.cfg file. The flag ensures that work does not conflict. Use "-local" only if you are planning on running more than one instance of Folding@Home on the same machine (this is only useful if you are running on a multi-processor machine). Create as many directories as there are processors on the machine, copy the exe files and client.cfg file into each of these directories, run "FAH3Console -local -config" on each and specify unique machine IDs for each directory (under the Advanced Settings option). From then onwards you may run each copy by switching to its directory and running with the -local flag. Note You can only run one instance of the SS or GUI per system. This means that if you want to run other instances at the same time(a dually for example) then you have to run the Console(text) version for the second client using the -local flag. -help Print out the command line flags available and then exit. Applicable to client ver. 4.0 only Linux Specific -freeBSD For use by those wishing to use the Linux client on a machine running FreeBSD. See our FAQ for details on how to do this, but with this flag, all Cores downloaded will automatically be branded as being a Linux executable. Applicable to client ver. 4.0 only Windows Specific The below options are accepted but ignored by the clients for operating systems other than Microsoft Windows. -pause Pause after finishing and trying to send current unit. Allows a user to shut down after finishing a unit, by pressing Ctrl-C, without then getting new work to process. This is recommended if you are planning on shutting down your machine for a long time (e.g. for a vacation), or are planning to un/re-install F@H after finishing the currently processing work unit. -service Run in service mode (for programs such as firedaemon). This prevents the client from exiting when it detects the current user is logging out. If this option is used when the client is not run as a service then it will run normally, but will not shut down automatically if the user logs out, and a "Wait for program to close." dialog box will be displayed. Additional details are available here and here. Addtional information on implementing the flags can be found here.
got feedback?by wafen got feedback?by nozero got feedback?by nozero Please note: When you get to the Stanford site, you'll notice that it says "recommended client for all Windows versions". Please, ignore this and scroll down to "Windows 95/98/ME/NT/2000/XP "No-nonsense" text-only console" or the console version for your OS. You won't be sorry. Many problems arise for users of the graphical client. Just ask in the forums, you'll see.
got feedback?by Axilla
got feedback?by MstrBlstr0 | |||||||||||||
| Thursday, 24-May 13:04:26 | Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo over 12.5 years online © 1999-2012 dslreports.com. |
