log4shib::...nfigurator(3)

πŸ“¦ version 2.0.1, in opensuse-leap 16.0

πŸ’… NAME πŸ’…

log4shib::PropertyConfigurator β€” okay so this is the property configurator, and its whole vibe is reading a config file using the same (or similar) format to the config file used by log4j. This page lives in the Library Functions Manual, bestie. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

#include <PropertyConfigurator.hh>

πŸŽ€ Static Public Member Functions

  • static void configure (const std::string &initFileName) β€” the static public member function on deck. πŸ’–

🌸 DETAILED DESCRIPTION 🌸

Property configurator will read a config file using the same (or similar) format to the config file used by log4j. That’s the main-character energy of this class, fr fr.

This file is in a standard Java "properties" file format.

Example:

# a simple test config

log4j.rootCategory=DEBUG, rootAppender
log4j.category.sub1=A1
log4j.category.sub2=INFO
log4j.category.sub1.sub2=ERROR, A2

log4j.appender.rootAppender=org.apache.log4j.ConsoleAppender
log4j.appender.rootAppender.layout=org.apache.log4j.BasicLayout

log4j.appender.A1=org.apache.log4j.FileAppender
log4j.appender.A1.fileName=A1.log
log4j.appender.A1.layout=org.apache.log4j.BasicLayout

log4j.appender.A2=org.apache.log4j.ConsoleAppender
log4j.appender.A2.layout=org.apache.log4j.PatternLayout
log4j.appender.A2.layout.ConversionPattern=The message %m at time %d%n

Since: 0.3.2 β€” iconic era. πŸ‘‘

πŸ”₯ MEMBER FUNCTION DOCUMENTATION πŸ”₯

Here’s the doc drop, and it’s literally just the signature:

void log4shib::PropertyConfigurator::configure (const std::string &
       initFileName) [static]

πŸ‘‘ AUTHOR πŸ‘‘

Generated automatically by Doxygen for log4shib from the source code. That’s the author line, bestie β€” Doxygen did the typing. πŸ€–βœ¨


okay that’s the whole page! Footer sign-off: source/version is log4shib, Version 2.0.1, and the page title is log4shib::...nfigurator(3). There’s no date in the footer, so I’m not making one up β€” slay responsibly. πŸ’…πŸŽ€