Please check the troubleshooting section for "Cannot open your terminal" error
I'm going to think about add a daemon tools like you suggested but I prefer to use supervisord I think it's more modern and easy to use.
For the reboot problem, please can you paste me your /etc/rc.local file?
May be when you save the settings from Minera it cannot write the rc.local file, so double check 1) rc.local permission should be 777(-rwxrwxrwx) 2) the content of rc.local
If you find your permissions wrong run:
sudo chmod 777 /etc/rc.local
Then go to settings and save them (when you click the save button Minera recalculate the command string and overwrite the rc.local file)
Please let me know
PS
I just added a cool temperature widget, wait for the next release
Thanks for getting back to me. Also thanks for the troubleshooting tip. I tried what it said and it worked.
The permissions of rc.local are world executable, as you've indicated:
-rwxrwxrwx 1 root root 426 May 10 13:24 /etc/rc.local
Of course since minerd is running at boot, I don't think it's a permissions problem. It's just not hashing or behaving properly.
Here's the contents of rc.local:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
su - minera -c "/usr/bin/screen -dmS cpuminer /var/www/minera/minera-bin/minerd --config /home/minera/config/minerd.config"
exit 0
FYI, the config file is world readable:
-rw-r--r-- 1 minera minera 808 May 10 13:35 /home/minera/config/minerd.config
Here's my config file contents (with my user info obscured):
{
"gc3355-detect" : true,
"freq" : "850",
"gc3355-freq" : [
"/dev/ttyACM2:950:0", "/dev/ttyACM2:925:1", "/dev/ttyACM2:925:2", "/dev/ttyACM2:925:3", "/dev/ttyACM2:925:4",
"/dev/ttyACM1:900:0", "/dev/ttyACM1:875:1", "/dev/ttyACM1:900:2", "/dev/ttyACM1:900:3", "/dev/ttyACM1:900:4",
"/dev/ttyACM0:875:0", "/dev/ttyACM0:900:1", "/dev/ttyACM0:900:2", "/dev/ttyACM0:900:3", "/dev/ttyACM0:900:4"
],
"pools" : [
{
"url" : "stratum+tcp://sf.clevermining.com:3333",
"user" : "user",
"pass" : "x"
},
{
"url" : "stratum+tcp://doge.ghash.io:3333",
"user" : "user.minecraft",
"pass" : "x"
},
{
"url" : "stratum+tcp://uswest.wafflepool.com:3333",
"user" : "user_minecraft",
"pass" : "x"
}
],
"debug" : true
}
Note that I'm using a newer version of cpuminer that supports the "pretty" config file format for device frequencies. Also, I've changed the binary at /var/www/minera/minera-bin/minerd to a symlink to my built and installed version. I did this because I want to be able to rev versions of cpuminer separately from Minera.
As an aside, I realize that if there are API differences it could result in breakage between Minera and my version of cpuminer, but so far you and Sandor111 have keep pretty well in sync. Doesn't seem like I'm living too dangerously...
Just to be sure, I checked and there's only one copy of minerd running (it looks like two, but the first one is screen):
~$ ps auxwww | grep -i [m]inerd
minera 2362 0.0 0.0 5512 1472 ? Ss May10 0:08 /usr/bin/SCREEN -dmS cpuminer /var/www/minera/minera-bin/minerd --config /home/minera/config/minerd.config
minera 2363 0.4 0.1 99152 3080 pts/3 Ssl+ May10 4:07 /var/www/minera/minera-bin/minerd --config /home/minera/config/minerd.config
Maybe the issue is that the rc.local mechanism is starting cpuminer too soon in the boot cycle? Maybe the "gc3355-detect" is failing when run too early? Again, I should mention that I'm running under Ubuntu 12.10 on my test rig. It's not a Raspberry Pi.
I'm not that familiar with the rc.local launch mechanism. Maybe there's a way to delay running until later in the boot process? Or perhaps I could change it to call a script that waits for kernel resources (like the network) to be up before starting minerd.
Regarding daemontools verses supervisord, I don't have a strong preference. I'm just used to daemontools, and I like D. J. Bernstein's work. But either package would be fine.
Again, thanks for getting back to me. Minera is really an awesome application. I've tried MineNinja and Scripta. Minera, in combination with Sandor111's cpuminer, is hands down the best I've used so far. You both should be proud of your work.