daqinterface fails to boot the system when there are no boardreader log files
This is probably a low-priority issue, but I've noticed that when I start with a freshly installed system, daqinterface fails to boot the system until there are one or more boardreader*.log files in the boardreader log subdirectory.
#1 Updated by John Freeman over 3 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
I'm dealing with this via commit 360720e3157bb64abc72cd444b80b3b5579a7e7e. DAQInterface will check for the logfiles up to five times (with a 2-second pause between each check) before giving up. This way on a freshly-installed system a little time will be granted for the logfiles to show up before an exception is thrown.