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 rolled over. In
other terms, the big logfile gets closed and a new one is opene
gt;> 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 th
> 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
Hello folks,
any chance this one is ever fixed?
https://bugs.php.net/bug.php?id=51860
I am a customer of 1&1. They told me they will not upgrade until this
one is fixed. Imagine that there are thousands of customers running
php 5.2.17 just because of this issue. Unfortunately I am not able to
fix
4 matches
Mail list logo
