Project

General

Profile

Bug #15356

daqinterface fails to boot the system when there are no boardreader log files

Added by Kurt Biery almost 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
artdaq-daqinterface
Target version:
-
Start date:
01/28/2017
Due date:
% Done:

100%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

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.

Associated revisions

Revision 360720e3 (diff)
Added by John Freeman almost 3 years ago

JCF: in response to Kurt's Redmine Issue #15356, I've added logic whereby DAQInterface will check the logfile directory for the expected logfiles up to five times before giving up and throwing an exception

History

#1 Updated by John Freeman almost 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.

#2 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to artdaq-daqinterface


Also available in: Atom PDF