|Main Archive Page > Month Archives > syslog-ng-users archives|
On 2011-10-22 07:10, Balazs Scheidler wrote:
> I wanted to publish a last maintenance release from the 3.2 branch
> before moving on to work on 3.4.
> I've backported the relevant patches, tests have ran (both on my
> development computer and a separate build environment), but I'd like to
> ask anyone running 3.2.x to test it in more production-like
> The current state is available in git, but I've also uploaded a tarball
A couple of systemd packaging notes:
* the tarball includes two identical syslog-ng.service files
The second one can be dropped as the first is the one thats
gets installed (--withsystemdsystemunitdir)
* the syslog-ng.service file in the 3.2 branch is different from the
one in the 3.3 git tree:
--- syslog-ng-3.2.git/contrib/systemd/syslog-ng.service ...
+++ syslog-ng-3.3.git/contrib/systemd/syslog-ng.service ...
@@ -6,6 +6,7 @@
ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
ExecReload=/bin/kill -HUP $MAINPID
* we have been experiencing very strange systemd/syslog-ng problems
in Fedora 15 (and Fedora 16 Beta): some systems become completely
unusable if we change the Sockets option in the syslog-ng.service
file from syslog-ng.socket to syslog.socket as suggested by the
systemd author. At the same time the line "StandardOutput=null"
was also added to the syslog-ng.service file but it doesn't
appears to be the source of the problem. Any help tracking this
one will be appreciated ...
The change that appears to be causing the problems:
-- Josť Pedro Oliveira * mailto:firstname.lastname@example.org * ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq