Stop being hard headed.
The test for: if [ blah > “776”.. is a fail always comparison on that line.
You need to treat that as a variable and access the value itself. That is $blah.. or ${blah} as many will use
-j
> 776 runs 1 command and if its over 776 runs something else. Not too hard to understand.
Right now because of the typo it may set a blank line if you bypass otherwise you just type in what you want and save and all is ok. If you try to bypass then you get what you get. The 3 typos are fixed already took 2 minutes.
Also the typos didnt stop you from mining it only set the wrong value in a config file which the web gui uses not cgminer.
In the end all that matters is the ability to control the freq and voltage, I dont think users care how I coded it. Maybe I kept it a cluster fuck to confuse people and something more is going on, never know.
I can always add some encryption but why
I honestly don't know why I try to help you.
YOUR TEST WILL ALWAYS GO TO THE SECOND CONDITION, *_NEVER_* THE FIRST CONDITION unless you make it a variable by simply prepending the test with a $. that's it, That's all I'm trying to say. I'm trying to explain a _bug_ in your implementation.
.... and "maybe i kept it a clusterF to confuse people" is laughable.
Go have whomever wrote your javascript fix your shell scripts; they will have better luck.
... also, it is impossible to fix the race condition in monitorcg, so no, you have not fixed it.
-j
