[syslog-ng] About lost of messages after syslog-ng stop

[Frank Abel Cancio Bello]

Hi all!

What can I do to avoid that when I stop my syslog-ng client and apache
server still logging to its files not lost all those messages? I mean,
in the time that the syslog-ng client was not running, the apache
continue working and logging data, but when I start the syslog client it
don't send to the syslog-ng server the messages that apache logging when
it was stopped.

Here is part of what I think relevant of my configuration file:


# apache message source
source s_apache {
# Apache2 access log source.
file("/var/log/apache2/access.log"
log_prefix("apache_access: ")
follow_freq(1)
flags(no-parse)
);

# Apache2 access log source.
file("/var/log/apache2/error.log"
log_prefix("apache_error: ")
follow_freq(1)
flags(no-parse)
);
};


# central log server
destination d_tcp { tcp("10.8.2.227" port(514)); };

# apache logs to central server.
log {
source(s_apache);
destination(d_tcp);
flags(flow-control);
};

All work fine, just worry about the lost of messages in case that the
communication with syslog-ng server fail. I know that Premium Edition
have the log_disk_fifo_size(), but that is the only way of do this?
Nobody have a workaround for this so necessary feature using the Open
Source Edition?


Salute
Frank Abel




__________________________________________

Participe en Universidad 2008.
11 al 15 de febrero del 2008.
Palacio de las Convenciones, Ciudad de la Habana, Cuba
http://www.universidad2008.cu