nturner commented on pull request #62:
URL: https://github.com/apache/logging-log4cxx/pull/62#issuecomment-921184615


   Sorry; been busy. Yes, @rm5248, if I use a configuration like the example in 
LOGCXX-523, logging appears to continue. That approach results in a more 
complex configuration (2x the number of appenders) and the failure behavior 
isn't as graceful. 
   
   Since the specific conditions where fork() is likely to fail are pretty well 
understood and the appropriate behavior in the context of GZCompressAction is 
pretty straightforward, I think I'll stick with the approach in this PR in my 
own local builds of log4cxx. Perhaps it's not good enough for upstream -- 
that's fine. :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to