<p dir="ltr">Yes, both rsyslog and sysklogd implement syslog protocol just like syslog-ng.</p>
<p dir="ltr">Sysklogd only supports UDP, which is lossy.</p>
<p dir="ltr">Rsyslog also supports TCP but the version you are referencing is ancient.</p>
<p dir="ltr">Syslog-ng keeps its opened connections alive when reloaded, with restarts those connections are closed and then reopened.</p>
<p dir="ltr">Inflight messages can get lost, which the client assumes were sent and the server didn't receive them. To overcome this limitation something like rltp or relp is needed.</p>
<p dir="ltr">Hth<br>
</p>
<div class="gmail_quote">On Aug 22, 2013 5:35 PM, "subin" <<a href="mailto:subin@opensourcesolutions.co.in">subin@opensourcesolutions.co.in</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I have syslog-ng v3.1.3-3 on Debian 6 listening on a network interface.<br>
<br>
1. Is it possible/compatible for syslog-ng to receive messages over<br>
network from sysklogd(v1.4.1-17) and rsyslog(v3.18.6-4)?<br>
<br>
2. In the event of syslog-ng getting restarted (part of logrotate<br>
scripts) would the messages be queued up on the remote syslog services?<br>
Or would<br>
there be any loss of log-data?<br>
<br>
Thanks.<br>
<br>
<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a href="http://www.balabit.com/support/documentation/?product=syslog-ng" target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.balabit.com/wiki/syslog-ng-faq" target="_blank">http://www.balabit.com/wiki/syslog-ng-faq</a><br>
<br>
</blockquote></div>