File _patchinfo of Package patchinfo.1810

<patchinfo>
  <packager>czanik</packager>
  <category>recommended</category>
  <rating>moderate</rating>
  <summary>syslog-ng: update to 3.4.2 and a additional fix</summary>
  <description>This udpate fixes the following issues with syslog-ng:
- update to 3.4.2, which fixes bnc#815746 and many other bugfixes, including flags(final)
  + loggen will bail out earily if using Unix sockets without a path specified.
  + Using the same filter for multiple destinations does not trigger a crash anymore.
  + An issue with log branch propagation has been fixed, restoring compatibility with the 3.3 branch (this mostly affected flags(final) use cases).
  + The systemd unit file now specified Restart=on-failure.
  + Support for empty blocks in the configuration were restored, syslog-ng does not crash anymore when encountering one.
  + An assertion was fixed in patterndb, that prevented one from overriding built-in values, such as HOST.
  + The persist state file (syslog-ng.persist) is now marked close-on-exec, so it does not leak through to forked subprocesses.
  + The system() source now treats /proc/kmsg as optional: if it is not readable to the user running syslog-ng, it will not be included.
  + Proper escape handling in backtick insertion has been implemented, so string arguments to block parameters are - again - treated correctly
  + A rare race condition in the SQL, MongoDB, SMTP and AMQP destinations have been fixed.
  + A possible deadlock was fixed within the suppress() handling code.

- Fix systemd unit to do only what is required by http://www.freedesktop.org/wiki/Software/systemd/syslog. In particular it should not mess with the ordering of syslog.target
- bnc#805309: Fixed to use program() instead of message() to match by program names.</description>
  <issue tracker="bnc" id="805309">syslog-ng: NetworkManager entries in /var/log/messages instead of /var/log/NetworkManager</issue>
  <issue tracker="bnc" id="815746">syslog-ng stops logging, "systemd-journal[249]: Forwarding to syslog missed 22 messages."</issue>
</patchinfo>