Another instance of dropped messages, but all statics records from syslog-ng indicate that no messages were dropped. Here is the logging path Server C - syslog-ng 2.0.8 - file destination - tcp destination A - tcp destination B Server A - syslog-ng 2.0.8 Linux 2.6.x - tcp source - pipe destination Server A - syslog-ng 2.0.8 linux 2.6.x - pipe source with flow-control - file destination Server B - syslog-ng 2.0.8 Linux 2.6.x - tcp source - pipe destination Server B - syslog-ng 2.0.8 linux 2.6.x - pipe source with flow-control - file destination Server C logged 608955 messages Server A logged 351502 messages Server B logged 179874 messages None of the servers record any dropped messages. syslog-ng does not report dropped messages on file destinations, but with the flow-control any drops should occur at the server that writes to the pipe. Anyone want to propose an explanation? Evan