i was able to run the second instance with all three parameters but I am more confused..

The intent was to reroute messages from production instance to dev instances on the same machine and take out a selected steam of logs on a different port.

rather than just the selected stream the second instance can see all the logs. Both the instances are listening on different ports.

Port 514- gets logs from two products (say windows and unix) i write Windows to disk and route the unix logs on say port 517 (to second instance)

Second instance is configure to write anything that it receives to a file.

To my surprise the above file has logs for Windows and there is no network exchange at all.

Could it be that the second instance internally confusing sources and destinations?

On Wed, Mar 5, 2014 at 3:23 AM, Evan Rempel <erempel@uvic.ca> wrote:

The persistence file is used to store the progress on the sources. If the source is from the network, then there
isn't any progress, or stated differently, the concept of progress does not apply.

If the source is reading from a file, then there is a "current position" in the file. If syslog-ng is stopped for
a few minutes and then started again, it will resume from where it left of in the file.

The control file can be used to send commands to a running instance of syslog-ng. You can get statistics and do other things.
Best to read the manual on syslog-ng-ctl

Evan.

On 03/04/2014 01:18 PM, Shashank Rohatgi wrote:
> Evan
>
> Thank you for your reply. I am new to syslog-ng on command line. Can you also explain what are a persist and control files?

______________________________________________________________________________
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