fix(syslog): open syslog channel on write#53738
Conversation
provokateurin
left a comment
There was a problem hiding this comment.
I'm not familiar with syslog, but I don't understand how this change affects the tag. All it does is calling openlog() later and on every write, but the tag is only set once and never changed.
|
It's for when apps need their own loggers and are configured to use syslog with a custom tag in addition to core's logger. The admin_audit app instantiates its own |
|
Ok but when it creates the instance it can pass the tag already and openlog will be called with it, no? |
|
Yes, but that's what has been causing the bug in the linked issue. What currently happens is core calls |
|
Ahhh that totally makes sense. Please include such information in the PR description, so the reason why it was broken and how this fixes it is clear from the start. |
My bad 😅 I'll make sure to do that next time. |
|
/backport to stable31 |
|
/backport to stable30 |
This fixes a bug where only one tag gets used when multiple tags have been configured (e.g. different tags for 'syslog_tag' and 'syslog_tag_audit') Signed-off-by: Kent Delante <kent.delante@proton.me>
01edfbf to
eb58d2b
Compare
Summary
This fixes a bug where only one tag gets used when multiple tags have been configured (e.g. different tags for 'syslog_tag' and 'syslog_tag_audit')
Checklist