Summary: | Koha::Logger dies when log4perl.conf has FileAppender files with different owners, also compatibility with logrotate | ||
---|---|---|---|
Product: | Koha | Reporter: | Olli-Antti Kivilahti <olli-antti.kivilahti> |
Component: | Architecture, internals, and plumbing | Assignee: | Olli-Antti Kivilahti <olli-antti.kivilahti> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | david, jonathan.druart, kyle, martin.renvoize, mirko, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | 14167 | ||
Bug Blocks: | |||
Attachments: |
Bug-16509-Koha-Logger-dies-when-log4perl.conf-has-Fi.patch
Bug 16509: fix multi-owner perms, improve logrotate compatibility |
Description
Olli-Antti Kivilahti
2016-05-12 16:39:15 UTC
Created attachment 51458 [details] [review] Bug-16509-Koha-Logger-dies-when-log4perl.conf-has-Fi.patch Olli, this patch doesn't apply to master. I think this must be dependent on another bug. Created attachment 90944 [details] [review] Bug 16509: fix multi-owner perms, improve logrotate compatibility Rescued, because the last CLI section no longer exists. The patch still applies, but how can I test this? In which case do we have such situations? I am marking this as INVALID for now, as to me we should not face it with our current infrastructure. Please reopen with more details if you think it's still valid. |