 Con Kolivas
|
d5d8c2cc5b
Implement an older header fix for a label existing before the pthread_cleanup macro.
|
14 years ago |
|
Con Kolivas
|
5081c1824a
Limit the number of curls we recruit on communication failures and with delaynet enabled to 5 by maintaining a per-pool curl count, and using a pthread conditional that wakes up when one is returned to the ring buffer.
|
14 years ago |
|
Con Kolivas
|
d4405de704
Generalise add_pool() functions since they're repeated in add_pool_details.
|
14 years ago |
 Luke Dashjr
|
06023e549e
Bugfix: Return failure, rather than quit, if BFwrite fails
|
14 years ago |
|
Luke Dashjr
|
4ba9006d0e
Disable failing devices such that the user can attempt to re-enable them
|
14 years ago |
|
Luke Dashjr
|
124ee9b28a
Bugfix: thread_shutdown shouldn't try to free the device, since it's needed afterward
|
14 years ago |
 Kano
|
afa3fa56b6
API bool's and 1TBS fixes
|
14 years ago |
|
Kano
|
09fe8bcb12
Icarus - minimise code delays and name timer variables
|
14 years ago |
|
Kano
|
524e2fb8f2
api.c V1.9 add 'restart' + redesign 'quit' so thread exits cleanly
|
14 years ago |
|
Kano
|
01c93bc1d4
api.c bug - remove extra ']'s in notify command
|
14 years ago |
|
ckolivas
|
5cf4e188fd
Increase pool watch interval to 30 seconds.
|
14 years ago |
|
ckolivas
|
85008a7853
Reap curls that are unused for over a minute.
|
14 years ago |
|
Con Kolivas
|
ec3d057016
Use the ringbuffer of curls from the same pool for submit as well as getwork threads.
|
14 years ago |
|
Con Kolivas
|
7d288eac9f
Implement a scaleable networking framework designed to cope with any sized network requirements, yet minimise the number of connections being reoped.
|
14 years ago |
|
Con Kolivas
|
89053c78da
There is no need for the submit and getwork curls to be tied to the pool struct.
|
14 years ago |
|
ckolivas
|
adda6e6680
Do not recruit extra connection threads if there have been connection errors to the pool in question.
|
14 years ago |
|
ckolivas
|
7638511290
We should not retry submitting shares indefinitely or we may end up with a huge backlog during network outages, so discard stale shares if we failed to submit them and they've become stale in the interim.
|
14 years ago |
|
Con Kolivas
|
0171c84e75
Bump version number to 2.3.6
|
14 years ago |
|
Con Kolivas
|
e8eeea4cfc
More NEWS.
|
14 years ago |
|
Con Kolivas
|
b015348df4
Shorten stale share messages slightly.
|
14 years ago |
|
Con Kolivas
|
7233890d85
Protect the freeing of current_hash under mutex_lock to prevent racing on it when set_curblock is hit concurrently.
|
14 years ago |
|
Con Kolivas
|
10f619cb2f
Update NEWS.
|
14 years ago |
|
Con Kolivas
|
53c22551f7
Change default behaviour to submitting stale, removing the --submit-stale option and adding a --no-submit-stale option.
|
14 years ago |
|
Con Kolivas
|
f9123f0587
Make sure to start the getwork and submit threads when a pool is added on the fly.
|
14 years ago |
|
Con Kolivas
|
5ad942d187
Faster hardware can easily outstrip the speed we can get work and submit shares when using only one connection per pool.
|
14 years ago |
|
Con Kolivas
|
60cc425ff8
Bump version number to 2.3.5
|
14 years ago |
|
Con Kolivas
|
628ac19977
Get rid of confusing "waiting on fresh work" part of longpoll message to minimise log width and add pool number to longpoll work restart message.
|
14 years ago |
|
Con Kolivas
|
06bf44b06f
Restarting cgminer leads to a socket that can't be bound for 60 seconds, so increase the interval that API binding waits to 30 seconds to minimise the number of times it will retry, spamming the logs.
|
14 years ago |
|
Con Kolivas
|
972860c0af
Remove unused variable.
|
14 years ago |
|
Con Kolivas
|
3362a2a447
Give a longpoll message for any longpoll that detects a block change, primary or backup, and also display which pool it was.
|
14 years ago |
