6 Commits

Author SHA1 Message Date
Randy MacLeod fee1274169 syslog-ng: upgrade 4.7.0 -> 4.8.1
Release notes:
   https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.8.1
   https://github.com/syslog-ng/syslog-ng/releases/tag/syslog-ng-4.8.0

Update the syslog-ng.conf.[systemd|sysvinit] files to align with
upstream's 4.8 version. This involved changing from stats_freq(0)
to stats(freq(0)) to avoid:
   > WARNING: Your configuration file uses an obsoleted keyword, ...
as was done in:
   2d3a8c783 packaging: Update the sample Debian config to not throw warning
The comments and the greater authentication/encryption defaults kept.
Note that the latter are comment lines.
Also kept a line from the 'Sources' section:
   file("/proc/kmsg" program_override("kernel"));
but it's not clear if that's needed. It was in the original meta-oe version of
the file from 2018, version 3.15 but not the upstream syslog-ng-3.15.1.

With systemd enabled using poky-altcfg, there's a warning:
   /etc/tmpfiles.d/syslog-ng.conf:1:
      Line references path below legacy directory /var/run/,
      updating /var/run/syslog-ng → /run/syslog-ng;
      please update the tmpfiles.d/ drop-in file accordingly.
but that was present in the previous version and I won't take time
to fix it right now since systemd + syslog-ng isn't a common combination.

Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-03-27 17:16:16 -07:00
Aurélien Bertron e80ce510e1 fix(syslog-ng): warning about conf version
The service warned on startup about running in compatibility mode since the configuration version was "3.31" instead of "3.36".

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2022-07-02 11:37:03 -04:00
Yi Fan Yu 01d3f9daa0 syslog-ng: upgrade 3.24.1 -> 3.31.2
License-Update:
Reword and clarify which subdir is LGPLv.1 and GPLv2.

Patch-Removal:
* 0001-syslog-ng-fix-segment-fault-during-service-start.patch
https://github.com/buytenh/ivykis/commit/a5e9caddbdb4d9d85133a440edec6aa7c1f018ac

Submit pending patches upstream.

Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2021-04-17 07:43:10 -07:00
Jeremy Puhlman 19f622749e syslog-ng: Remove config nag on boot
[2020-02-16T22:13:56.331425] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslo
g-ng 3.24 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, a
nd once completed change the @version header at the top of the configuration file

Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-02-20 21:00:52 -08:00
Slater, Joseph ef9f2b31b2 syslog-ng: change conf files to version 3.19
Also add dns_cache(no) option to eliminate initialization warning.

Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2019-11-01 17:22:53 -07:00
changqing.li@windriver.com 6457b3d77d syslog-ng: fix syslog-ng startup problem with systemd
1. Fix syslog-ng service cannot startup after upgrade to 3.15.1

   1) Align path of syslog-ng.conf between syslog-ng@default
      and do_install in syslog-ng.inc
   2) create a default instance for syslog-ng
   3) Install default parameter file to /etc/default according
      to https://github.com/balabit/syslog-ng/commit
      /649d1151e79033cc2b81b3353917507266814436

2. Fix "Failed to acquire /run/systemd/journal/syslog socket,
   disabling systemd-syslog source;" accordint to below content
   from syslog-ng admin guide.

   1) for linux, If the host is running under systemd, syslog-ng
      OSE reads directly from the systemd journal file using the
      systemd-journal() source.
   2) If possible, use the more reliable systemd-journal() driver
      instead.
   3) The socket activation of systemd is buggy, causing some log
      messages to get lost during syst

Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2018-06-20 10:01:28 -07:00