Hi all,
as you are probably aware, 3.18.1 contains a "fix" for a format issue
with kernel messages. This fix has a somewhat broader scope. In an ideal
world, I would have preferred to run it through the beta phase and not
apply it directly to stable. But this is counter-productive, as the
format issue may affect users of v3-stable *right now*. So I am doing
the second best thing: I have prepared a preview tarball and hope that
some of you will implement it and tell me if it works OK. I do not
expect any problems, but, hey, there is always a difference between lab
and practice.
I have pushed back 3.18.1 in the hopes to get some feedback. I need to
release 3.18.1 soon, preferably by next Monday or Tuesday. So I would
appreciate any feedback you can offer (including "no problem
experienced" feedback).
The tarball is available at:
http://download.rsyslog.com/rsyslog/rsyslog-3.18.1-Test1.tar.gz
This most probably is the official 3.18.1, except for some changes to
cover the new release number (except, of course, feedback requires
changes).
Thanks,
Rainer
as you are probably aware, 3.18.1 contains a "fix" for a format issue
with kernel messages. This fix has a somewhat broader scope. In an ideal
world, I would have preferred to run it through the beta phase and not
apply it directly to stable. But this is counter-productive, as the
format issue may affect users of v3-stable *right now*. So I am doing
the second best thing: I have prepared a preview tarball and hope that
some of you will implement it and tell me if it works OK. I do not
expect any problems, but, hey, there is always a difference between lab
and practice.
I have pushed back 3.18.1 in the hopes to get some feedback. I need to
release 3.18.1 soon, preferably by next Monday or Tuesday. So I would
appreciate any feedback you can offer (including "no problem
experienced" feedback).
The tarball is available at:
http://download.rsyslog.com/rsyslog/rsyslog-3.18.1-Test1.tar.gz
This most probably is the official 3.18.1, except for some changes to
cover the new release number (except, of course, feedback requires
changes).
Thanks,
Rainer