| 1 |
Rich Freeman wrote: |
| 2 |
> |
| 3 |
> If you use emerge-webrsync then the sync operation itself should use |
| 4 |
> gpg signature checking and that should rule out server issues. Ditto |
| 5 |
> if you sync with git with the appropriate settings, though git also |
| 6 |
> has internal hash consistency checking (that doesn't prevent |
| 7 |
> intentional tampering but should catch data transmission issues). |
| 8 |
|
| 9 |
|
| 10 |
emerge-webrsync actually fixed it, it's running now. WTF^100.... |
| 11 |
|
| 12 |
Now it's only a problem of maxing out the load average on my Ryzen 1800x |
| 13 |
processor. =P |
| 14 |
|
| 15 |
Currently 10.0 with a throttle value of 12, 16 hardware threads are |
| 16 |
available.... |
| 17 |
|
| 18 |
-- |
| 19 |
Please report bounces from this address to atg@×××××××××.com |
| 20 |
|
| 21 |
Powers are not rights. |
Archives