Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Potential config file corruption
See original GitHub issueThis is a potential issue, I don’t think it actually happened yet.
In many places, RaspiBlitz currently uses echo "something=something" >> /mnt/hdd/raspiblitz.conf.
If the user manually modifies the config file, and for some reason removes the newline at the end (it’s unlikely, I just wanted to report this), this command will end up with the config file looking something like this:
Before:
oldConfig=oldValue
Expected:
oldConfig=oldValue
something=something
Actual config file:
oldConfig=oldValuesomething=something
In this scenario, doing echo "something=something" | tee -a /mnt/hdd/raspiblitz.conf would be better.
Even though this is unlikely you may find it’s worth fixing it, because it can be fixed by a simple search and replace.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Scripts works fine during the RCs. Closing this issue for v1.7.2 release.
OK change on the redis branch is in … ready for final testing