Ignore:
Timestamp:
Dec 27, 2011, 11:15:41 AM (10 years ago)
Author:
mitchb
Message:
Fix syslog-ng/systemd interaction, or "socket to me!"

systemd creates and passes datagram sockets to daemons (at least by
default).  Fedora's default configuration for syslog-ng expected the
socket passed in to be a stream socket (and we slurped that in forever
ago).  When syslog-ng sees that the socket it received isn't of the
type it expected, instead of either coping or barfing, it just opens
a new /dev/log socket of the type it wants, which is just hunky-dory
for programs that connect after it disowns systemd's socket, but for
anything that already connected to the datagram socket from systemd,
they're logging to a useless socket that systemd isn't poll()ing, and
thus can block (and, depending on what programs end up in this situation,
potentially wedge your entire system).  So, uh... let's not do that
anymore.  Fedora's also changing their default config.

See RHBZ #742624
File:
1 edited

Legend:

Unmodified
Added
Removed
Note: See TracChangeset for help on using the changeset viewer.