Project

General

Profile

Bug #22785

DAQInterface should handle situations where the hostname in the boot file and the hostname returned by gethostname differ

Added by John Freeman 3 months ago. Updated 3 months ago.

Status:
Reviewed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
06/20/2019
Due date:
% Done:

100%

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

Description

DAQInterface saves the names of a run's logfiles in the run record by looking in the directories where it determines the artdaq processes would have written them out. In the case of private subnets, this can cause issues - in SBND's case, a node might be listed as sbnd-daq33-priv in the boot file, but on that node, artdaq will write out logfiles into a subdirectory which contains the hostname "sbnd-daq33" - determined via the unistd.h function "gethostname" - rather than "sbnd-daq33-priv". DAQInterface should account for this possible discrepancy, perhaps by checking the value of the $HOSTNAME variable on the remote node.

Associated revisions

Revision 74690c6e (diff)
Added by John Freeman 3 months ago

JCF: fix for Issue #22785 - instead of using the hostname provided in the boot file to determine where the logfiles are, use the result of the "hostname" command as run on the node in question

History

#1 Updated by John Freeman 3 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved

This Issue's been resolved; it can be tested using the head of the feature/issue22785_better_logfile_locating branch, commit 88773c6f5cf99edfac8e7743271c794d228377d9

#2 Updated by Gennadiy Lukhanin 3 months ago

  • Status changed from Resolved to Reviewed


Also available in: Atom PDF