Hello Viktor, My logger binary is only ran on startup, so would mean the socket disappears again on next start. Also, it does close/unlink the socket whenever the program exits.
Met vriendelijke groeten, Niels Hofmans SITE https://ironpeak.be BTW BE0694785660 BANK BE76068909740795 > On 23 Aug 2018, at 19:53, Viktor Dukhovni <[email protected]> wrote: > > > >> On Aug 23, 2018, at 1:44 PM, Niels Hofmans <[email protected]> wrote: >> >> Hello guys, >> >> Just to let you know, it works perfect with the following piece of golang >> code I wrote: https://gist.github.com/HazCod/35d705ebf87704b976ceab58ba20ca21 >> >> So no need for full fledged syslog-ng in my container, only this binary that >> listens and prints to stdout. > > If the container image persists across restarts (which I'd expect is the case > for an MTA that might have queued mail) then this code may fail to start > if/when > /dev/log already exists. With unix-domain sockets a server typically needs to > unlink() the socket before creating and listening on a new one. > > -- > Viktor. >
