Top stocks, companies, and cryptocurrencies to invest in for the blockchain boom
5 stars based on
65 reviews
It is based on cgminer by Con Kolivas ckolivaswhich is in turn based on cpuminer by Jeff Garzik jgarzik. Documentation Documentation amd app sdk 2 8 bitcoin stock available in directory doc. For details on several topics, see: Note that most of the documentation is outdated. If you want to contribute, fork this repository, update as needed, and submit a pull request.
To compile a debug version, replace -O2 with -ggdb. Systemwide installation is optional. You may run sgminer from the build directory directly, or make install if you wish to install sgminer to a system location or a location you specified with --prefix. After saving configuration from the menu, you do not need to give sgminer any arguments and it will load amd app sdk 2 8 bitcoin stock configuration.
Any configuration file may also contain a single "include": Writing the configuration will save all settings from all files in the amd app sdk 2 8 bitcoin stock. All are available since CURL version 7. If you specify the --socks-proxy option to sgminer, it will only be applied to all pools that don't specify their own proxy setting like above. For more advanced usagerun sgminer --help. Runtime usage The following options are available while running with a single keypress: Current pool management strategy: G gives you something like: The 2 diff values are the actual difficulty target that share reached followed by the difficulty target the pool is currently asking for.
The output line shows the following: A 5 second exponentially decaying average hash rate avg: An all time average hash rate A: The total difficulty of Accepted shares R: The total difficulty of Rejected shares HW: The number of HardWare errors WU: Multipool Failover strategies A number of different strategies for dealing with multipool setups are available.
Each has their advantages and disadvantages so multiple strategies are available by user choice, as per the following list: Failover The default strategy is failover. This means that if you input a number of pools, it will try to use them as a priority list, moving away from the 1st to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will move back to the higher priority ones.
Round robin This strategy only moves from one pool to the next when the current one amd app sdk 2 8 bitcoin stock idle and makes no attempt to move otherwise. Rotate This strategy moves at user-defined intervals from one active pool to the next, skipping pools that are idle. Load balance This strategy sends work to all the pools on a quota basis. By default, all pools are allocated equal quotas unless specified with --quota. This apportioning of work is based on work handed out, not shares returned so is independent of difficulty targets or rejected shares.
While a pool is disabled or dead, its quota is dropped until it is re-enabled. Quotas are forward looking, so if the quota is changed on the fly, it only affects future work. If all pools are set to zero quota or all pools with quota are dead, it will fall back to a failover mode. See quota below for more information.
The failover-only flag has special meaning in combination with load-balance mode and it will distribute quota back to priority pool 0 from any pools that are unable to provide work for any reason so as to maintain quota ratios between the rest of the pools. Balance This strategy monitors the amount of difficulty 1 shares solved for each pool and uses it to try to end up amd app sdk 2 8 bitcoin stock the same amount of work for all pools. Quotas The load-balance multipool strategy works off a quota based scheduler.
The quotas handed out by default are equal, but the user is allowed to specify any arbitrary ratio of quotas. Quotas can be changed on the fly by the API, and do not act retrospectively. Setting a quota to zero will effectively disable that pool unless all other pools are disabled or dead. In that scenario, load-balance falls back to regular failover priority-based strategy. While a pool is dead, it loses its quota and no attempt is made to catch up when it comes back to life. To specify quotas on the command line, pools should be specified with a semicolon separated --quota or -U entry instead of --url.
Pools specified with --url are given a nominal amd app sdk 2 8 bitcoin stock value of 1 and entries can be mixed. Writing configuration files with quotas is likewise supported. To use the above quotas in a configuration file they would be specified thus: You can enable the pool whilst the miner is still running 'p' followed by 'e' followed by pool number - but the pool will still be disabled on restart if the config file is not changed. This allows the json file to contain a large number of pools, of which some could be automatically culled at start up.
This makes it easy to swap pools in and out of the runtime selection, without having a large list of pools cluttering up the display. A restart of the miner 's' followed by 'c' will reload the config file and any changes that may have been made. Logging sgminer will log to stderr if it detects stderr is being redirected to a file. There is also the -m amd app sdk 2 8 bitcoin stock on Linux which will spawn a command of your choice and pipe the output directly to that command.
The WorkTime details 'debug' option adds details on the end of each line displayed for Accepted or Rejected work done. An example would be: The previous hash is followed by the getwork mode used M: X where X is one of P: The argument to the option may be "-" for standard output not advisable with the ncurses UIany valid positive number for that file descriptor, or a filename. To log share data to a file named "share. Author Message raiogam Send message Joined: Message - Posted:
