File _patchinfo of Package patchinfo.2819

<patchinfo incident="2819">
  <category>recommended</category>
  <rating>low</rating>
  <packager>czanik</packager>
  <summary>syslog-ng: Update from 3.4.5 to 3.4.7 and one additional fix</summary>
  <description>This update fixes the following issues with syslog-ng:
- bnc#846762: use system(); for local logs
- update from 3.4.5 to 3.4.7 (bugfix release)
  + Node flag propagation has been fixed, so flags(final) works the same as it did in 3.3, when embedded log statements are used too.
  + Using the value-pairs() framework, either via the $(format-json) template function or any of the destinations that make use of it, will now correctly skip and ignore empty values, even in SDATA.
  + A file descriptor and memory leak has been fixed in the syslog() destination.
  + The pdbtool program will warn in test mode when a test message has no program attribute.
  + If the PID property is overwritten, syslog-ng will now stop using the cached MSGHDR value, and therefore, use the newly set PID instead, as it was supposed to.
  + The localport() option of various network destinations has been restored, and will work correctly now.
  + The upstart service file in contrib has been updated to use a different process mode (background), as we do not need a supervisor when running under upstart. This also means that upstart will be far less confused.
  + The system() source has been fixed on Solaris and HP-UX: it correctly recognises the system on Solaris, and uses /dev/log (and not /dev/pipe) on HP-UX.
  + The sun-streams() source has been fixed, it compiles and works again.
  + A very rare and short race condition has been fixed in the pipe() source and destination modules, which could leave the pipe available with elevated permissions for a short time.
  + The SQL, MongoDB and SMTP modules were fixed to not cause a segmentation fault when loaded before the socket module.
  + The syslog-format() module has been fixed to only set the PROGRAM to "kernel" if all of the previous conditions apply, and the message is a local message.</description>
  <issue tracker="bnc" id="846762">null bytes in /var/log/messages after reboot</issue>
</patchinfo>