configure separate stdout/err (console) log files
I have a vague recollection of discussing this in the past, but I think we may benefit from
having a place to record some of our thoughts on this.
Most messages in our system go through message facility which duplicates
the messages to 2 or 3 destinations: console, logfile, and msgviewer.
There are places in the code where messages go directly to stdout/err (i.e. console).
Is this a bug? Are there still places we cannot control?
Currently, direct process management has one stdout/err "log file" for all the processes
on a node and that file is in /tmp. Should there be separate files and/or should the files be
put under a LOG_ROOT?
The main advantage I see with a separate message facility configured file destination is that
all the messages in the file are guaranteed to have a controlled format.
#1 Updated by Eric Flumerfelt over 1 year ago
On feature/22925_RemoveCoutCerr in several of the repositories, I have either replaced or supplemented all std::cerr calls with TLOG as approriate.
I have also audited all of the printf/std::cout/std::cerr calls in our code, and all that are left are either in art modules or applications explicitly designed to be run from the command line.