> Assuming each thread has its own copy of $this->fp, even after renaming the
> log file all other threads will still be pointing at the old file. The
> resource is connected to the inode, not the filename, so even if the
> filename changes the inode does not, therefore the actual location on disk
On Wed, Jun 8, 2011 at 8:09 AM, Christian Grobmeier wrote:
> Hello,
>
> I am one of the log4php [1] hackers over at the ASF. We (thats Ivan
> Habunek and myself) have now a nasty issue for which we would be glad
> about input.
>
> Use case:
> Once the log file got a specific size, it will be rolle
Thanks guys.
I will test it together with Ivan and hopefully the user.
Never heard of this function before, very cool that you have
identified the problem so quickly.
Thanks again!
On Wed, Jun 8, 2011 at 11:41 AM, Richard Quadling wrote:
> On 8 June 2011 10:19, Frank Arensmeier wrote:
>> 8 ju
On 8 June 2011 10:19, Frank Arensmeier wrote:
> 8 jun 2011 kl. 09.09 skrev Christian Grobmeier:
>
>> The object itself is always the same, for all threads. Every thread
>> gets this "Appender" from a kind of a pool.
>>
>> My guess is, every thread gets some kind of a copy of this object,
>> workin
8 jun 2011 kl. 09.09 skrev Christian Grobmeier:
> The object itself is always the same, for all threads. Every thread
> gets this "Appender" from a kind of a pool.
>
> My guess is, every thread gets some kind of a copy of this object,
> working at it. Once it reaches the method, its members state
5 matches
Mail list logo
