One of the compile option for apache is -DBUFFERED_LOGS,
which buffers logs till they reach some size and then flushes them
(or when you kill apache).
Now I looked up, and they are out of order :
213.57.xx.xxx - - [04/Aug/2000:23:56:08 +0300] "GET /
213.57.xx.xxx - - [04/Aug/2000:23:55:54 +0300] "GET /
213.57.xx.xxx - - [04/Aug/2000:23:55:54 +0300] "GET /
213.57.xx.xxx - - [04/Aug/2000:23:55:54 +0300] "GET /
213.57.xx.xxx - - [04/Aug/2000:23:56:13 +0300] "GET /
213.57.xx.xxx - - [04/Aug/2000:23:56:02 +0300] "POST
213.57.xx.xxx - - [04/Aug/2000:23:55:55 +0300] "GET /
My setup pretty much the same (Mandrake 7, 2.2.14+Reiser).
Regards,
Evgeny
Ira Abramov wrote:
> a week passed and no one answered with an idea. anyone care to take a
> guess?
>
> to recap: Apache 1.3.12 on a plain vanilla Mandrake 7.1, standard-issue
> kernel 2.2.16+Reiser, instead of writing logs to the file in real time
> and synching, it just blocks until apache is killed or sent a SIGHUP,
> where it flushes the logs in one blow (accumulated sometimes over a
> week!) but out of sequence, to the log file. is that a bug or a feature?
>
> TIA,
> Ira.
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" in the message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
