[prev in list] [next in list] [prev in thread] [next in thread]
List: syslog-ng
Subject: Re: [syslog-ng] 3.13 maintenance branch
From: Scheidler, Balázs <balazs.scheidler () balabit ! com>
Date: 2018-01-09 21:44:28
Message-ID: CANWQT2PjfWKf5rGcifd+3sCZu0yTSmUvHF3wNtMFPM6S4tBpHA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
I only cherry picked changes from current master, so I can only pick that
patch if it is already fixed on master.
On Jan 9, 2018 09:51, "Fabien Wernli" <wernli@in2p3.fr> wrote:
> Hi,
>
> On Tue, Jan 09, 2018 at 08:56:35AM +0100, Scheidler, Balázs wrote:
> > At this point, I take this as an experiment: if publishing fixes this way
> > "works" (e.g. fixes get published in the OS packages that we don't
> maintain
> > ourselves), then we can get some form of maintenance to older open source
> > releases as time permits, with collaboration from our fellow OS
> > maintainers. Also, power users, who are able to compile source code for
> > themselves get help too.
> >
> > Let me know if this is useful.
>
> I love the idea, of course :-)
>
> That being said, and as it's related to the other major fix in the upcoming
> 3.13.2, I'd love to see this resolved:
>
> https://github.com/balabit/syslog-ng/pull/1800
>
> In a nutshell, the elastic-v2 destination silently drops messages when the
> ES cluster is gone. I think this is serious enough to justify a bugfix
> release on its own.
>
> What's blocking the merge is that I can't get *any* java logs to pop up
> anywhere, thus I don't see what's wrong with the current implementation of
> the fix.
>
> Sorry for trying to bump this into 3.13.2, but I really think this is
> important.
>
> ____________________________________________________________
> __________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?
> product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
[Attachment #5 (text/html)]
<div dir="auto">Hi,<div dir="auto"><br></div><div dir="auto">I only cherry picked \
changes from current master, so I can only pick that patch if it is already fixed on \
master.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jan 9, \
2018 09:51, "Fabien Wernli" <<a \
href="mailto:wernli@in2p3.fr">wernli@in2p3.fr</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br> <br>
On Tue, Jan 09, 2018 at 08:56:35AM +0100, Scheidler, Balázs wrote:<br>
> At this point, I take this as an experiment: if publishing fixes this way<br>
> "works" (e.g. fixes get published in the OS packages that we don't \
maintain<br> > ourselves), then we can get some form of maintenance to older open \
source<br> > releases as time permits, with collaboration from our fellow OS<br>
> maintainers. Also, power users, who are able to compile source code for<br>
> themselves get help too.<br>
><br>
> Let me know if this is useful.<br>
<br>
I love the idea, of course :-)<br>
<br>
That being said, and as it's related to the other major fix in the upcoming<br>
3.13.2, I'd love to see this resolved:<br>
<br>
<a href="https://github.com/balabit/syslog-ng/pull/1800" rel="noreferrer" \
target="_blank">https://github.com/balabit/<wbr>syslog-ng/pull/1800</a><br> <br>
In a nutshell, the elastic-v2 destination silently drops messages when the<br>
ES cluster is gone. I think this is serious enough to justify a bugfix<br>
release on its own.<br>
<br>
What's blocking the merge is that I can't get *any* java logs to pop up<br>
anywhere, thus I don't see what's wrong with the current implementation \
of<br> the fix.<br>
<br>
Sorry for trying to bump this into 3.13.2, but I really think this is<br>
important.<br>
<br>
______________________________<wbr>______________________________<wbr>__________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" \
rel="noreferrer" target="_blank">https://lists.balabit.hu/<wbr>mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" \
rel="noreferrer" target="_blank">http://www.balabit.com/<wbr>support/documentation/?<wbr>product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" rel="noreferrer" \
target="_blank">http://www.balabit.com/wiki/<wbr>syslog-ng-faq</a><br> <br>
</blockquote></div></div>
[Attachment #6 (text/plain)]
______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic