[bind10-dev] [Log4cplus-devel] request for feedback (fwd)

JINMEI Tatuya / 神明達哉 jinmei at isc.org
Mon May 21 16:56:24 UTC 2012


At Mon, 21 May 2012 13:43:28 +0200,
Shane Kerr <shane at isc.org> wrote:

> > 3. What do you miss in log4cplus?
> 
> Our main problems have to do with concurrent logging from multiple
> processes. 
> 
> If log4cplus used only a single write() statement, and O_APPEND, when
> writing to files then we would not have problems with files. We would
> still have issues when writing to the console or other slow devices
> (serial ports, etc.) since there is no guarantee that you will get your
> entire buffer output.
> 
> To work around this in a general way we use advisory locks via fcntl()
> to prevent concurrent logging. This seems to be the best solution, and
> it would be nice to have this capability in log4cplus itself.

IIRC, log4cplus dumps its own warning messages to stdout or stderr,
and they leak in an awkward way.  It would be nice if the application
can control whether/how these messages are dumped.

---
JINMEI, Tatuya


More information about the bind10-dev mailing list