Project

General

Profile

Bug #4083

Need to verify signal masking in multi-thread applications

Added by Christopher Green almost 7 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Needed Enhancements
Target version:
artdaq v3_00_01
Start date:
06/12/2013
Due date:
% Done:

0%

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

Description

It is important to make sure that signal masks are properly directed to the threads of an application best equipped to deal with them (e.g. art).

Related issues

Related to ds50daq - Feature #3958: Continue running when online monitoring is requested but the XPRA server is not runningNew05/29/2013

Related to art - Feature #4356: Document the pattern that artdaq applications should use to correctly handle signals [ds50daq-related]Closed07/17/201307/31/2013

Related to art - Feature #4355: Document and verify the signal handling within art [ds50daq-related]Closed07/17/201307/31/2013

History

#1 Updated by Kurt Biery almost 6 years ago

  • Target version set to 576
  • Estimated time set to 60.00 h

We should look into what is needed (for example, see Issues #4355 and #4356) and make the appropriate changes in artdaq.

It's probably documented in the related Issues, but a major driver for this issue was the desire to avoid having problems in online monitoring code (contributed by users) bring down the full DAQ [when we are still in the model of having the online monitoring Aggregator as part of the MPI program].

#2 Updated by Kurt Biery almost 6 years ago

Part of the changes related to this Issue may include "implementing an MPI wrapper or watchdog to complement the signal handling improvements and allow MPI to correctly terminate processes when one has exited abnormally." [Chris, 12-Jul-2013]

#3 Updated by Eric Flumerfelt about 3 years ago

  • Category set to Needed Enhancements
  • Target version deleted (576)

#4 Updated by Eric Flumerfelt about 2 years ago

  • Status changed from New to Closed
  • Target version set to artdaq v3_00_01

This is mostly no longer applicable to artdaq v3. art is run as a separate process, and therefore handles its own signals without affecting its parent artdaq process.

Also available in: Atom PDF