Project

General

Profile

Bug #22095

DAQInterface "direct" mode leaves stale processes

Added by Eric Flumerfelt 7 months ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/08/2019
Due date:
% Done:

0%

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

Description

I've been seeing many instances of processes, especially datalogger, being left over after a run_demo run using direct process management in DAQInterface.

I'm not sure if this is a failure in the DAQInterface cleanup logic, or artdaq handling a signal and not exiting as expected.

History

#1 Updated by John Freeman 6 months ago

Could you say a bit more on the conditions under which this happens? With artdaq-demo v3_04_00 installed on mu2edaq01 (~jcfree/artdaq-demo_v3_04_00), if I log in and set DAQINTERFACE_PROCESS_MANAGEMENT_METHOD to "direct", none of the following three scenarios causes leftover processes after I cd into ~jcfree/artdaq-demo_v3_04_00:

  • Simple execution of ./run_demo.sh
  • Execution of ./run_demo.sh where I kill the window in which DAQInterface was launched while it's still running
  • Modifying the ToySimulator so that it will hang on stop, and then executing ./run_demo.sh where a stop timeout occurs


Also available in: Atom PDF