Why do I continue to maintain #sysklogd on Linux when there's #rsyslog and #syslogng?
I believe what sysklogd has going for it is exactly what the competitors sacrificed: simplicity, a tiny footprint, zero dependencies beyond libc, and a config file a human can read in five minutes. On embedded systems, routers, and appliances that's not a consolation prize β it's the point.
Added basic #multicast functionality to #sysklogd today. And then my regression tests suddenly started failing β¦ on CI. Obviously work fine when run locally, and tests failing that are not related to the latest changes and worked fine the last weeks *sigh*
At least I know what Iβll be doing tomorrow.
Ah yes, Iβm done! Just completed program, hostname, and (generic) property based (incl RFC5424 properties!) filtering support for #sysklogd π€π€― The latter supports very powerful text matching, including regexp! Next release will probably be out tomorrow, first day of the new year!
Joachim Wiberg