I know that syslog-ng removes those sockets, but for Mag, the systemd workaround kicked in, which means that it was opening the socket from /var/run/<I don't know the path>/syslog and not /dev/log.

But maybe it was /dev/log before the upgrade or something. But anyway, he has found his socket now.

Bazsi

--
Bazsi

On Mon, Feb 22, 2016 at 10:51 AM, PÁSZTOR György <pasztor@linux.gyakg.u-szeged.hu> wrote:

Hi,

"Scheidler, Balázs" <balazs.scheidler@balabit.com> írta 2016-02-22 07:17-kor:
> Hmmm, maybe that symlink should have been there in the first place and
> something (syslog-ng even...) may have removed it.

I am almost sure, it was sng.
When it get a unix domain socket in it's config, it start to listen on it
in three steps:
* stat()
* unlink()
* bind()

Cheers,
Gyu

______________________________________________________________________________
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