Ok, thank you very much for the help.
Just to clarify once more.
Every 4 hour reboot:
1. SSH into miner
2. Type: echo '0 0 * * * /sbin/reboot' >> /Angstrom/Cointerra/crontab.root
No need for this step 2., the next one (3.) will still do this (4 is a factor of 12), but there's no harm in doing it
3. Type: echo '0 0,4,8,12,16,20 * * * /sbin/reboot' >> /Angstrom/Cointerra/crontab.root
Anything else need to be done after this? (Save, quit etc)
Nothing other than a reboot. The file is saved, but the *actual* crontab isn't loaded yet, so a reboot is necessary.
And just to cover my steps again, if I wanted to disable the automatic reboot and bring it back default, would it be this?:
1. SSH into miner
2. Type: echo '0 0 * * * /sbin/reboot' >> /Angstrom/Cointerra/crontab.root
This isn't necessary either; again, if you do the following command in step 3., it doesn't matter if you perform step 2. or not.
3. Type: echo '*/5 * * * * /opt/restart_cgminer.sh' > /Angstrom/Cointerra/crontab.root
Thank you again for the help
I agree, my original post was a little terse. The unix way of *appending* the output of a program to a file is the '>>' syntax. To overwrite the entire contents of a file with the output of a program, you use the single '>' syntax. 'echo' is just a way to send some text to the "standard output" so that the '>>' or '>' syntax works.
If you run the command 'crontab -l' you'll get the output of what the system is currently using for cronjobs ("chronological jobs"). You'll notice that after you run 'echo '0 0 * * * /sbin/reboot' >> /Angstrom/Cointerra/crontab.root', you'll only see one line from 'crontab -l' before rebooting (the original one put in by Cointerra). *After* rebooting, it should have loaded the contents of what's in the file /Angstrom/Cointerra/crontab.root, which should contain the new reboot jobs.
Clear as mud? PM me if you need further clarification. Power cycling electronics isn't good, but this shitty hack might very well be worth the mild hurt.