[syslog-ng] 3.2.5 preparations - systemd

[Jose Pedro Oliveira]

On 2011-10-23 07:55, Balazs Scheidler wrote:
---[snip]---
> 
>>  * 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:
>>       -Sockets=syslog-ng.socket
>>       +Sockets=syslog.socket
>>
>>    More details:
>>    https://bugzilla.redhat.com/show_bug.cgi?id=742624
> 
> hmm... I seem to remember having a problem with systemd acquired sockets
> to remain in blocking mode. This was fixed after 3.2.4 was released in
> this patch:
> 
> commit 2f214c4f87d944aa28d53e331a67b1fd88d9840f
> Author: Balazs Scheidler <bazsi at balabit.hu>
> Date:   Wed Jun 22 12:50:53 2011 +0200
> 
>     systemd: make sure the acquired fd is in non-blocking mode
>     
>     The fd acquired from systemd is in blocking mode, and syslog-ng
>     didn't explicitly set it to non-blocking, causing syslog-ng
>     to stall. This patch changes that, explicitly enables
>     O_NONBLOCK and O_CLOEXEC on systemd acquired fds.
>     
>     Reported-By: Enrico Scholz <enrico.scholz at informatik.tu-chemnitz.de>
>     Signed-off-by: Balazs Scheidler <bazsi at balabit.hu>

We had already backported it to the 3.2.4 release without success:
https://bugzilla.redhat.com/show_bug.cgi?id=742624#c14

jpo
-- 
José Pedro Oliveira
* mailto:jpo at di.uminho.pt *