Václav Haisman
Václav Haisman
You can compile log4cplus as single-threaded but then you cannot use it in multi-threaded process. You can use multi-threaded log4cplus in forking process but you *must* `exec()`. Regardless of whether...
As I have written elsewhere, you must `exec` after you have `fork`ed. There is no other way. You cannot just re-initialize log4cplus like `if (fork()==0){ /* reinit */ }`. If...
This is not a limitation of the library. This is a limitation of the POSIX model of things.
Well, no. The only situation, when it worked better in 1.x with respect to the forking, is when you never create any threads in your application. Version 2.x does start...
I am tempted to provide a setting that would disable the thread pool entirely, not even compile the source for it. But that does not solve anything with respoect to...
> When you say "create/have any threads in your application" then I suppose you mean log4cplus threads. Because I can create any application threads I want, and fork after that...
> That is not true. It is actually true as far as I know. > Could you separate these two? log4cplus threads go, locking stays? I have added an option...
@Harika-Bavana You have the option to disable the thread pool. It is still enabled by default.
I do not understand the question here. Are you asking for away to find out the file name of the current log file? I think this is doable. You would...