New answers tagged

1

your source seems to be misconfigured a bit: source s_remote { tcp(port(514)); syslog(transport(tcp)); }; This is actually two sources: the first line listens on port 514 for RFC3164 messages the second line listens for RFC5424 messages on port 601 (the default port of the syslog() source) So if you send your RFC5424 message to port 601, it ...


0

I ran into this recently with a customer who had need of really long Apache httpd logs (which is no problem even with old versions of modern syslog daemons like rsyslog.) To deal with this, I created logger clones in some scripting languages without any legacy message-size restrictions. See: GitHub: ryran/loggerclones - The nix logger command ...



Top 50 recent answers are included