On Wed, Apr 18, 2018 at 9:29 PM, Eric Covener wrote:
> On Wed, Apr 18, 2018 at 3:18 PM, Hemant Chaudhary
> wrote:
>> Thanks Eric
>>
>> It means thread are using lock so that one thread/process can write a time.
> I believe it's unlocked, I think posix promises they will not be
> interleaved if wr
On Thu, Apr 19, 2018 at 8:36 AM, Rainer Canavan
wrote:
> On Wed, Apr 18, 2018 at 9:29 PM, Eric Covener wrote:
>> On Wed, Apr 18, 2018 at 3:18 PM, Hemant Chaudhary
>> wrote:
>>> Thanks Eric
>>>
>>> It means thread are using lock so that one thread/process can write a time.
>> I believe it's unloc
On Wed, Apr 18, 2018 at 3:18 PM, Hemant Chaudhary
wrote:
> Thanks Eric
>
> It means thread are using lock so that one thread/process can write a time.
I believe it's unlocked, I think posix promises they will not be
interleaved if written through a shared file descriptor.
Thanks Eric
It means thread are using lock so that one thread/process can write a time.
Right ?
On Apr 19, 2018 12:35 AM, "Eric Covener" wrote:
> On Wed, Apr 18, 2018 at 2:33 PM, Hemant Chaudhary
> wrote:
> > Hi Team,
> >
> > How apache writes to access_log or error log. Whether it opens File
On Wed, Apr 18, 2018 at 2:33 PM, Hemant Chaudhary
wrote:
> Hi Team,
>
> How apache writes to access_log or error log. Whether it opens File
> Descriptor(FD) for each request/connection to write in log file.
Logs are opened by the parent process at startup and the file
descriptors are inherited by
Hi Team,
How apache writes to access_log or error log. Whether it opens File
Descriptor(FD) for each request/connection to write in log file.
Thanks
Hemant
