v1.0.6 2017-03-06
- 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.
- added support for native JSON number formats
supported by parsers: number, float, hex
- added support for creating unix timestamps
supported by parsers: date-rfc3164, date-rfc5424
- fixed build problems on Solaris
Version 2.0.3, 2017-03-22
- add ability to load rulebase from a string
- bugfix: string parser did not correctly parse word at end of line
- bugfix: literal parser does not always store value if name is specified
Version 2.0.2, 2016-11-15
- bugfix: no error was emitted on invalid "annotate" line
- "annnotate": permit inline comments
- fix a problem with cross-compilation
- bugfix: abort in literal path compaction when useing "alternative" parser
- bugfix: lognormalizer could loop
- fix misleading compiler warning
- testbench: add test for "annotate" functionality
Version 2.0.1, 2016-08-01
- fix public headers, which invalidly contained a strndup()
definition
- fix some issues in pkgconfig file
- enhance build system to natively support systems with older
autoconf versions and/or missing autoconf-archive.
Version 2.0.0, 2016-07-21
- completely rewritten, much feature-enhanced version
- requires libfastjson instead of json-c
- big improvements to testbench runs, especially on travis
- lognormalizer tool can now handle lines larger 10k characters
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Version 1.1.2, 2015-07-20
- permit newline inside parser definition
- new parser "cisco-interface-spec"
- new parser "json" to process json parts of the message
- new parser "mac48" to process mac layer addresses
- new parser "name-value-list" (currently inofficial, experimental)
- some parsers did incorrectly report success when an error occurred
- call "rest" parser only if nothing else matches.
- new API to support error callbacks
- testbench is now enabled by default
- bugfix: misadressing on some constant values
- bugfix: add missing function prototypes
Version 1.1.1, 2015-03-09
- fixed library version numbering
- added new parser syntaxes
- bugfix: function ln_parseFieldDescr() returns state value due
to unitialized variable. This can also lead to invalid returning
no sample node where one would have to be created.
liblognorm shall help to make sense out of syslog data, or, actually,
any event data that is present in text form.
In short words, one will be able to throw arbitrary log message to
liblognorm, one at a time, and for each message it will output
well-defined name-value pairs and a set of tags describing the message.
