On Mon, 23 Aug 2004 11:10:14 -0400, Brian Akins [EMAIL PROTECTED] wrote:
I know buffered logs is experimental, but I found a feature. If the
parent has to send SIGTERM or SIGKILL to a child, the child does not
flush it's buffer. Is there any quick fix?
there's no fix at all for flushing
Jeff Trawick wrote:
if not appropriate to run the normal file cleanups at child exit, then
mod_log_config could have a child exit hook to flush buffered log
files
Does child_exit exist in 2.0?
--
Brian Akins
Senior Systems Engineer
CNN Internet Technologies
At 10:37 AM 8/23/2004, Brian Akins wrote:
Jeff Trawick wrote:
if not appropriate to run the normal file cleanups at child exit, then
mod_log_config could have a child exit hook to flush buffered log
files
Does child_exit exist in 2.0?
plog is the appropriate pool cleanup to accomplish what you
William A. Rowe, Jr. wrote:
At 10:37 AM 8/23/2004, Brian Akins wrote:
Jeff Trawick wrote:
if not appropriate to run the normal file cleanups at child exit, then
mod_log_config could have a child exit hook to flush buffered log
files
Does child_exit exist in 2.0?
plog is the
The plog pool, second in the argument list to the open_logs call,
is used for log files. It sounded like you were trying to deal
with log file flushing, which is why I suggested this pool's cleanup.
Bill
On Mon, 23 Aug 2004 11:37:23 -0400, Brian Akins [EMAIL PROTECTED] wrote:
Jeff Trawick wrote:
if not appropriate to run the normal file cleanups at child exit, then
mod_log_config could have a child exit hook to flush buffered log
files
Does child_exit exist in 2.0?
oops,
On Mon, 23 Aug 2004 16:06:28 -0400, Jeff Trawick [EMAIL PROTECTED] wrote:
On Mon, 23 Aug 2004 11:37:23 -0400, Brian Akins [EMAIL PROTECTED] wrote:
Jeff Trawick wrote:
if not appropriate to run the normal file cleanups at child exit, then
mod_log_config could have a child exit hook to
