Currently, the behavior of our output modules is inconsistent. RootOutput and RootDAQOut appear to crash art when they fill up their target partition, which causes the DAQ to first restart art then stop taking data via back-pressure (artdaq gives up on restarting art when it doesn't live long enough after starting). BinaryFileOutput appears to silently fail, and continues to consume events.
It may be desirable to have BinaryFileOutput behave the same way as RootOutput, and have SharedMemoryEventManager perform some action upon determining that art is no longer capable of running.
This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/23837 (FNAL account required) Originally created by @eflumerf on 2020-01-07 19:29:36
Currently, the behavior of our output modules is inconsistent. RootOutput and RootDAQOut appear to crash art when they fill up their target partition, which causes the DAQ to first restart art then stop taking data via back-pressure (artdaq gives up on restarting art when it doesn't live long enough after starting). BinaryFileOutput appears to silently fail, and continues to consume events.
It may be desirable to have BinaryFileOutput behave the same way as RootOutput, and have SharedMemoryEventManager perform some action upon determining that art is no longer capable of running.