Ok, sorry, scratch that patch (for now). BFGMiner refuses to start during boot.
I'm truly sorry for not testing this crucial part before submitting the patch, but the init script works flawlessly if it's run after boot-time, so I assumed it was ready; but for an unknown reason, during boot, bfgminer fails to contact the pool and exits immediately without bothering to retry or wait a bit. When I noticed this, at first I thought I messed up the dependencies so that bfgminer started before the network was up, but I tried all sorts of combinations (even finally resorting to $all, which runs the init script almost in last position - only rc.local and rmnologin are run after that), to no avail. I'm struggling with this since yesterday and still didn't find a way to make it work at boot. I'm sure it's not a network issue because during my tests, I tried to telnet the port on the pool host from within the init script, and it worked. bfgminer's debug mode isn't very useful either, the only additional information it provides is about hardware detection. I really don't understand what's going on. If bfgminer wasn't happy with a single lagging/slow pool, it shouldn't work after boot either; but it does. I'll try to ask upstream if they can help me with this. Sorry again for the noise. Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
