Project

General

Profile

Feature #18152

Have FileDumperOutput output into messagefacility streams

Added by Gianluca Petrillo about 3 years ago. Updated about 3 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Christopher Green
Category:
Application
Target version:
-
Start date:
11/08/2017
Due date:
% Done:

0%

Estimated time:
2.00 h
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

FileDumperOutput output currently unloads everything on std::cout.
A dedicated messagefacility category would allow control on that output, and to resolve it from the rest of the art and non-_art_ code also dumping on std::cout.

History

#1 Updated by Kyle Knoepfel about 3 years ago

  • Status changed from New to Feedback

We are able to provide a dedicated messagefacility category for FileDumperOutput printout. However, note that doing so would require configuration a separate messagefacility destination to allow only FileDumperOutput output to be routed to that (e.g.) file.

Please let us know if that is acceptable. Otherwise, Marc's suggestion of just allowing a filename configuration parameter for FileDumperOutput is simple to implement.

#2 Updated by Gianluca Petrillo about 3 years ago

I favour the solution with messagefacility, that gives more power to the user. But I can work with either.

#3 Updated by Christopher Green about 3 years ago

  • Status changed from Feedback to Assigned
  • Assignee set to Christopher Green
  • Estimated time set to 2.00 h

Also available in: Atom PDF