Hi everyone, there's an open issue about log4cxx not blocking signals and therefore behaving somewhat badly.
https://issues.apache.org/jira/browse/LOGCXX-431 This is issue is being worked on currently, but a question came up about if to block signals by default, leave that decision to devs in code or provide some config to switch blocking vs. not blocking by default. https://github.com/apache/logging-log4cxx/pull/68#discussion_r695277961 Additional configs might not be necessary at all compared to only one line of code otherwise necessary. Keeping the current behaviour is backwards compatible and how things have always been, so won't break too much most likely. OTOH, if the current default behaviour is PITA for a lot of users, it might be worth changing it. So what's user's opinion about this? Thanks! Mit freundlichen Grüßen Thorsten Schöning -- AM-SoFT IT-Service - Bitstore Hameln GmbH Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK E-Mail: thorsten.schoen...@am-soft.de Web: http://www.AM-SoFT.de/ Tel: 05151- 9468- 0 Tel: 05151- 9468-55 Fax: 05151- 9468-88 Mobil: 0178-8 9468-04 AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska
