CMS MessageLogger: Adjusting Linebreak Policy

CMS MessageLogger Service
Adjusting Linebreak Policy

By default, output destinations (but not log4cplus or fwkJobReport destinations) are formatted by injecting line breaks between items if a line would exceed 80 characters. This formatting can be controlled and/or disabled:
process TEST = {

 service = MessageLogger {
    vstring destinations = {   "detailedInfo.txt"
                             , "critical.txt"
                           }
    PSet critical.txt     = { bool noLineBreaks = true   }
    PSet detailedInfo.txt = { int32  lineLength = 132    } 
  }
  untracked PSet maxEvents = {untracked int32 input = 5}
  path p = { myAnalysisModule }
  module myAnalysisModule = ModuleThatIssuesMessages { }
  source = EmptySource { }
}
The bool noLineBreaks = true parameter in the PSet configuring critical.txt tells the destination producing the file critical.txt not to add line breaks which would format the message for an 80-column screen. Files which will be parsed by automated utilities might be easier to handle without logger-produced line breaks within a message.

The int32 lineLength = 132 parameter in the PSet configuring detailedInfo.txt tells the destination producing the file detailedInfo.txt not format the message for a 132-column window.

USCMS Software and Computing Home Page - CMS MessageLogger Service Page - Configuration File


Mark Fischler
Last modified: November 29, 2005