They're dropped, lost, unrecoverable. There really is nothing else syslog-ng could do in those situations. If your data is that important (and who logs un-important stuff, anyway?) you should write it to a log file, and the parse it from there; that way, if your parser dies, you don't lose any data. On Mon, 28 Feb 2005 00:02:01 -0600, torpedo <torpedo@bluebottle.com> wrote:
I have the confusion regarding logs which are not read by the Destination programs.
In case of FIFO, if the destination program which is reading the logs from syslog-ng is slow and unable to sysnchronise with the syslog-ng and there is also a limit for the fifo buffer(amount of data it holds) then where does thoses logs goes , are those logs recoverable.
In other case of FIFO, if there is no destination program reading the logs from the FIFO what happens to the logs which are collected by the syslog-ng are those logs droped.