Open Tyler-R opened 8 years ago
You can confirm this behavior by using cat on /usr/bin/suitcontroller which should output binary data, then restarting the beaglebone, and then using cat on /usr/bin/suitcontroller again, which is when you will observe that there is no output from the command.
This may be caused by how I have my code on my local machine, NFS from the Beaglebone onto my local machine and then build on the Beaglebone, which may cause file corruption / permission issues (currently investigating).
It appears like over time a file in the same location with the same name will eventually begin to not save between reboots. Thus it currently looks like the solution is to give the binary file a new name or store it in a different folder.
The contents inside of the /usr/bin/suitcontroller file are being deleted whenever the system is restarted. This does not occur if you move the executable to /root/suitcontroller and change the systemctl script to run the executable in the new file location.