• If the configuration specifies a UNIX domain socket, and this socket already exists in the filesystem, consumer.Syslogd will fail with [2017-07-24 00:26:19 CEST] ERROR Failed to open unix:///tmp/gol.sock PluginID=SyslogdConsumer PluginType=consumer.Syslogd instead of simply reusing the existing socket

• In the above situation, despite the "Error" during startup, Gollum doesn't terminate.

• When shutting down, consumer.Syslogd doesn't remove this socket from the filesystem

• Specifying a UDP or TCP transport for a protocol that only supports the other causes a "Warning" instead of a fatal error and termination.

• When listening on a UNIX socket and running with Format: "RFC5424" or "RFC6587", transmitting a message with logger -u /tmp/gol.sock dadwqewqe123213123 [1] produces only an empty string in the Gollum message. Test results of all formats and transports:

# RFC3164 UNIX  OK
# RFC3164 UDP   OK
# RFC3164 TCP   N/A
#
# RFC5424 UNIX  error - empty msg
# RFC5424 UDP   OK
# RFC5424 TCP   N/A
#
# RFC6587 UNIX  error - empty msg
# RFC6587 UDP   OK
# RFC6587 TCP   OK

[1] Debian 9 x86_64, logger from bsdutils 1:2.28.2-1

• consumer.Syslogd doesn't provide syslogd-specific fields (facility, prio, etc) as Gollum metadata fields