[syslog-ng] [Bug 125] [systemd] refuses stop request from systemctl on socket activated start

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=125


Balazs Scheidler <bazsi at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|                            |FIXED
             Status|NEW                         |RESOLVED




--- Comment #3 from Balazs Scheidler <bazsi at balabit.hu>  2011-06-24 14:22:32 ---
Indeed, it was a problem in syslog-ng, and is fixed by this patch.

It only affects syslog-ng if it is really socket activated, which it isn't on Fedora 15. I'm not sure about other Linux distributions though.

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>


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.