New Logo Selected
The logo was originally contributed in 2014 by “robert s”, whom unfortunately I am no longer able to contact. While before we never officially adopted it, it went into widespread use and is already often used to represent rsyslog. So in a sense the now-official selection let’s us keep consistent.
We are glad to have the community decision. I am right now implementing the new logo all over rsyslog web spaces. It will also be available via the rsyslog website github project (PR just created).
Many thanks to all who voted. It was a pleasant experience for us. This may have also set stage for future polls on different topics.
Help select a logo…
We need a new, a real logo. We have some candidates. Note that logo 1 was originally contributed in 2014 by “robert s” (whom I no longer able to contact…). Unfortunately, we did never officially adopt it, primarily due to failure on my part. Nevertheless it got pretty popular on the Internet and is often associated with rsyslog.
Please let us know what you like by leaving either a comment here or posting to the mailing list. Alternatively, you can also cast your ballot via this online vote form.
We are of course open for any additional suggestions. We are also not upset if you let us know that we are not great logo designers – we know we are not ;-)
In order to avoid past errors, I ask anyone to provide feedback within one week, so we will draw a “winner” by Feb, 8th 2018. To help facilitate the decision I will experimentally put logo 1 into some places tomorrow if there is no strong objection in doing so.
If you want to have a look at our old old ugly logo have a look at e.g. https://hub.docker.com/u/rsyslog/)
My personal 2cts: I as rsyslog maintainer (@rgerhards) have to admit that I have a strong preference for either logo 1 or logo 2. Pro-logo 1 speaks IMHO that it is already associated with rsyslog. Together with its stylish simplicity, this makes it an excellent choice. I also need to say that I am a bit skeptic in regard to logo 6, simply because it breaks “r” and “syslog”.
librelp 1.2.14
librelp 1.2.14 [download]
This new release of librelp provides an API extension: add relpSrvSetMaxDataSize().
For more details, please take a look at the changelog below.
– API extension: add relpSrvSetMaxDataSize()
Thanks to Nathan Brown for the patch.
sha256sum: 11f6241a4336358a33bfdadd43ef299e8258db0a5243d0c164499c6b85ae5955
LibLogging 1.0.6 released
liblogging 1.0.6 [download]
We have released liblogging 1.0.6.
sha256sum: 338c6174e5c8652eaa34f956be3451f7491a4416ab489aef63151f802b00bf93
– fix small memory leaks in libstdlog
each open/close leaked a couple of bytes; this was no problem, except if
they were called very often. However, it was a problem when using memory
debuggers, which rightfully complained.
– fix BSD build
– enhancement: sigsafe_printf now recognizes the “j” length modifier
Thanks to David A. Bright for implementing this
– fix: build_file_line and build_syslog_frame call the __stdlog_print_*
functions incorrectly
Change these functions so that they call the __stdlog_print_* functions
with the correct buffer size.
see also: https://github.com/rsyslog/liblogging/issues/33
Thanks to David A. Bright for the patch.
– Implement a STDLOG_PID option
… to specify that each log message should be tagged with the process
identifier as well as the ident.
Thanks to David A. Bright for implementing this
– bugfix: potentialSEGV in the stdlog_sigsafe_string formatter
if NULL pointer was passed in
Thanks to David A. Bright for the patch
– bugfix: stdlog_sigsafe_printf mis-handles an int or unsigned int
Thanks to David A. Bright for the patch
– build system: auto-detect presence of journal libraries
simplifies build for most users. Many complained on mailing list
about missing journal dependency. Now by default we disable it if
the libs are not found, what usually is the right thing to do.
librelp 1.2.13
librelp 1.2.13 [download]
This new release of librelp provides only a few changes and cleanups.The biggest change is that librelp now builds on BSD.
For more details, please take a look at the changelog below.
– make build under BSD
– bugfix: duplicated lines after server reconnect
Thanks to Hervé for the patch.
sha256sum: 38df3ca7feba55850602bbefe3ac3c035e7666691d46b8bfbff1f1a4c774c0c7
librelp 1.2.12
librelp 1.2.12 [download]
This new release of librelp provides a few changes and cleanups. It provides an API enhancement to permit to set a connection timeout and it has some dynamic tests added to allow the use of rsyslog to test librelp.
For more details, please take a look at the changelog below.
– API enhancement: permit to set connection timeout
Thanks to Nathan Brown for the patch.
– cleanup: replace deprecated GnuTLS data types by current ones
– CI improvements: added dynamic tests
we now use the rsyslog testbench to do dynamic librelp tests. This
currently happens only under Travis CI.
sha256sum: 0355730524f7b20bed1b85697296b6ce57ac593ddc8dddcdca263da71dee7bd7
librelp 1.2.11
librelp 1.2.11 [download]
This new release of librelp is mostly a bugfixing release that fixes several issues, especially a potential segfault. The new version also has an API enhancement that adds a configurable connection timeout.
For more details, please take a look at the changelog below.
– bugfix: do not accept more than one “open” verb on a connection
closes https://github.com/rsyslog/librelp/issues/37
– bugfix: potential segfault when high-numbered fd is used in sender
When a fd (socket) with value >= 1024 was used by the client sender
process, the library could segfault in select(). This depended a bit
on the platform.
This patch solves the issue by replacing the select() call with
poll(). Note that we do not changed to epoll(), because
(a) we only wait on a single fd
(b) poll() is more portable
closes https://github.com/rsyslog/librelp/issues/38
– bugfix: make librelp not run in thight loop when out of sockets
If the process can no longer accept new connections (via accept)
because it has reached its file handle maximum, librelp runs in
a thight loop until either the client connection request is aborted
or a file handle becomes available.
This happens due to the fact that we get event notifications on
connection requests. As we can’t satisfy it, we librelp always
retries. Unfortunately, there is no socket call to cancel a
connection request, so we cannot push the client request out.
An alternative solution would be to close and re-open the
listening socket, but in that case it is uncertain if we ever can
re-aquire a socket (an easy DoS). So the best thing we can
probably do is delay retries a bit. We must be careful, however,
not to use a too long delay, as that would also affect other
connections. We could address that problem via a dedicated thread
for the listening process, but librelp is designed so that it can
be used by callers with any threading library and threading model,
and that would violate this design principle.
Judging the alternatives, a slight delay probably is the best
solution, especially as the situation is uncommon and will hopefully
not last too long. This patch implements that solution.
closes https://github.com/rsyslog/librelp/issues/34
– bugfix: flush the current recv frame if it exists if the client
session is restarting
Thanks to Nate Brown for the patch.
– API enhancement: add configurable connection timeout
Thanks to Nate Brown for the patch.
sha256sum: 84de48f46caba0106d8853af572aa7b625c82dfbcf5f7cd13d2e57cce786e929
librelp 1.2.10
librelp 1.2.10 [download]
This new release of librelp fixes a problem with sending large buffers, improves sender/receiver code and enables compatibility with older versions of GnuTLS.
– make compatible with older versions of GnuTLS which require
libgcrypt
– improve example sender/receiver code
Thanks to Chris Pilkington for the patches.
– bugfix: Send full buffers after connection re-establishing
When sending large buffers it’s possible that only part of buffer data
will be transferred before connection is closed. Then on connection
re-establishing librelp thinks part of buffer is already sent and
transfers only remaining part. Remote side then is not be able to parse
such message and always closes the connection.
Thanks to github user cellscape for the patch.
sha256sum: 6c80eed5e29061d2cce35408ae43ddaee354edc27c1076eabec6da4eaecdcc72
librelp 1.2.9
librelp 1.2.9 [download]
This is a bugfixing release of librelp.
– bugfix: Ignoring return status when handling syslog frames now.
Otherwise valid messages in the frame buffer will get lost when the
remote connection is closed during meantime.
– build bugfix: GnuTLS header was required even if TLS was turned off
Thanks to Pedro Alvarez Piedehierro for the patch.
– bugfix: correct wrong assert() calls [debug mode only affected]
sha256sum: 520de7ba3dc688dc72c5b014dc61ef191e9528f77d1651ddca55fc0c149d98a3
librelp 1.2.8
librelp 1.2.8 [download]
This is a bugfixing release of librelp. It fixes a segfault that occurs if KEEPALIVE is used.
sha256sum: 2623a4146e55b2b79508832998b3017b23d0dd683729c20c572034a1743cb2e3