Yes, both rsyslog and sysklogd implement syslog protocol just like syslog-ng.

Sysklogd only supports UDP, which is lossy.

Rsyslog also supports TCP but the version you are referencing is ancient.

Syslog-ng keeps its opened connections alive when reloaded, with restarts those connections are closed and then reopened.

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.

Hth

On Aug 22, 2013 5:35 PM, "subin" <subin@opensourcesolutions.co.in> wrote:

Hi,

I have syslog-ng v3.1.3-3 on Debian 6 listening on a network interface.

1. Is it possible/compatible for syslog-ng to receive messages over
network from sysklogd(v1.4.1-17) and rsyslog(v3.18.6-4)?

2. In the event of syslog-ng getting restarted (part of logrotate
scripts) would the messages be queued up on the remote syslog services?
Or would
    there be any loss of log-data?

Thanks.


______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq

______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq