anatoly techtonik | 4 Jun 10:34 2010
Picon

Re: [Trac-dev] Log concurrency issues?

Is the problem actual for mod_wsgi?

It wouldn't hurt to add process id in Trac log anyway.
-- 
anatoly t.

On Thu, Jun 3, 2010 at 7:49 PM, Noah Kantrowitz <noah <at> coderanger.net> wrote:
> You can always use a backend like syslog that prevents this if you are
> worried.
>
> --Noah
>
> On Jun 3, 2010, at 7:58 AM, Dexter, Gordon M. wrote:
>
>> I was looking into the logging code and I found that trac doesn't do much
>> customization; just a standard python logging object.  That should work fine
>> in some cases, since the Python logging object is thread-safe.  However it's
>> not fully concurrency-safe for multiple processes, and we use Trac through
>> mod_python, meaning there are always at least two apache processes running
>> at any one time.  The trac log is env specific, but the environment isn't
>> linked to a specific apache process, so it sounds like it's possible to lose
>> log events.  Is there something I'm missing (e.g. special handling in
>> mod_python) that prevents this?
>>
>> --Gordon
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Trac Development" group.
(Continue reading)


Gmane