From: Pavel Antokolsky aka Zigmar (zigmar_at_[hidden])
Date: 2005-07-02 13:30:14
On 6/30/05, Greg Landrum <greg.landrum_at_[hidden]> wrote:
> martin.ecker_at_[hidden] wrote:
> This was exactly the problem; adding a call to
> boost::logging::set_log_caching(false) cleared up the ordering problems.
>
> I had misunderstood the purpose of log caching.
It is a behaviour described in documentation. The caching is turned on
by default, in order to allow the entries logged _before_ log
initialisation not to be lost.
-- Best regards, Zigmar