Google Git
Sign in
apache / logging-log4cxx / 1dff96c7b194b943f69e3aca34a2615a3607da5a
commit1dff96c7b194b943f69e3aca34a2615a3607da5a[log] [tgz]
authorStephen Webb <stephen.webb@ieee.org>Tue Sep 06 21:00:48 2022 +1000
committerGitHub <noreply@github.com>Tue Sep 06 21:00:48 2022 +1000
treebe35539b0e0f0f03a414b02a9237ea664101454a
parentd74edc6bbb1b30e0ccf4cd2e7d998a25a4d52e31 [diff]
Stop all file watch dog instances in LogManager::shutdown(). (#121)

This PR aims to address LOG4CXX-451.

Also included is support for automatic start of a watchdog when using automatic configuration by providing a positive integer value in the LOG4CXX_CONFIGURATION_WATCH_SECONDS environment variable.
10 files changed
tree: be35539b0e0f0f03a414b02a9237ea664101454a
  1. .github/
  2. src/
  3. .asf.yaml
  4. .astylerc
  5. .editorconfig
  6. .gitattributes
  7. .gitignore
  8. CMakeLists.txt
  9. doap_log4cxx.rdf
  10. INSTALL
  11. KEYS
  12. liblog4cxx-qt.pc.in
  13. liblog4cxx.pc.in
  14. LICENSE
  15. NOTICE
  16. README.md
  17. sonar-project.properties
README.md

Issues and pull requests

Issues are maintained in the Apache JIRA by default, so before posting pull requests, please have a look there if an associated issue with your problem/feature/... exists already. If not, it‘s generally OK to directly create pull requests IF code is already available, but please be somewhat verbose: Provide some background information about what actual problem the PR solves, why this needs to be solved etc. Don’t just provide commits about the fact that you changed something.

If any discussion is needed before actually having any code, simply create a ticket in JIRA or send a message to the corresponding mailing list. Thanks!