liblogging 1.0.6 [download]We have released liblogging 1.0.6. This release mostly provides fixes for different issues, like a small memory leak, build detection for journal libraries and many more. For full details, see the changelog below. sha256sum: 338c6174e5c8652eaa34f956be3451f7491a4416ab489aef63151f802b00bf93 —————————————————————————- v1.0.6 2017-03-06– fix small memory leaks in libstdlog each open/close leaked a couple of bytes; this was […]
liblogging 1.0.5 [download]We have released liblogging 1.0.5. This release has a important bugfix for a bug that caused the date stamp to be partially incorrect. The day part was totally off and this affected the “uxsock:” and “file:” drivers. sha256sum: 310dc1691279b7a669d383581fe4b0babdc7bf75c9b54a24e51e60428624890b —————————————————————————- v1.0.5 2014-12-09– cleanup for systemd-journal >= 209 closes https://github.com/rsyslog/liblogging/issues/17– bugfix: date stamp was incorrectly […]
liblogging 1.0.3 [download]We have released liblogging 1.0.3. This is a pure bug-fixing release fixing some build problems and clarifying part of the API. sha256sum: c9da7e4e01c0912085e9393dfb9d59bbd355c80a4ac5484d78bbfdfa91d011c0 v1.0.3 2014-03-18– fix build problem in Ubuntu 10.04 Thanks to Assaf Gordon for reporting See: https://github.com/rsyslog/liblogging/issues/11– do not override user varibale CFLAGS Thanks to Thomas D. for reporting this problem and suggesting […]
liblogging 1.0.2 [download]We have released liblogging 1.0.2. This is the first release with a basically feature-complete liblogging-stdlog component. It is an enhanced replacement for the syslog(3) API which supports multiple channels, signal-safeness, and logging drivers for syslog, the systemd journal, unix sockets, and files. While this version is suitable for use with applications, we still […]
liblogging 1.0.1 [download]This version primarily clarifies the licensing and fixes some packaging issues. Otherwise, it is identical to 1.0.0.Changelog:v1.0.1 2014-02-10– rfc3195 component now 2-clause BSD licensed This means the complete liblogging is now under 2-clause BSD– new component names: * liblogging-stdlog * liblogging-rfc3195 made some necessary name adjustments See also: https://github.com/rsyslog/liblogging/issues/2sha256sum: 99d09101cc3c22e2388fe2a817bb1c6f5fe2275623aadb94a49d1c2259102bfa
liblogging 1.0.0 [download]We have released liblogging 1.0.0.This release now has the rfc3195 library as optional component and we added the libstdlog component which is used for standard logging. sha256sum: b74b456e21d08465dc5a52b1bbbc6a00caa313186cea4751c6eccf468fc84cfa
After a very long time, LibLogging 0.6.0 has been released today. This version is not as stable as 0.5.0, but it includes the COOKED listener as its most important feature (but please note that it currently does not support COOKED relay operations or is scheduled to do that in the near future).
You may wonder… no news during the past month. Is LibLogging abandoned? Well, it looks like it is … but that’s not the truth. Of course, development on LibLogging has stopped, a fact caused by the simple matter of lack of interest in the library. However, there is growing interest since spring of this year […]
It comes with the addition of a client-side COOKED profile (not yet on the server side) as well as a full-blown message object.
This version is the first one to include support for building servers (listeners). Please note that there is NO 0.3.0 version – this number was eaten up by an incomplete copy passed on to some limited folks. . . . . . . . .