Apache configuration piped log configuration explanation.

[carock]

I think you may want to re-word or maybe explain a little better the Apache piped log configuration setting.

This text on that item, " This option will reduce the number of log files Apache manages, which will free system resources." can be 100% false.

For example, one of my servers has 695,035 log files within /usr/apache/domlogs directory. This is wasting disk space resources and also causing problems with backup jobs because of the number of files.

 

[SimpleSonic]

I think you may want to re-word or maybe explain a little better the Apache piped log configuration setting.

This text on that item, " This option will reduce the number of log files Apache manages, which will free system resources." can be 100% false.

For example, one of my servers has 695,035 log files within /usr/apache/domlogs directory. This is wasting disk space resources and also causing problems with backup jobs because of the number of files.

Can you explain a little better why you are finding this "100% false"?

If you disable it, your log files would increase. So how is that not saving you resources having it enabled?

Or maybe you're seeing something I am not here?

 

[carock]

Can you explain a little better why you are finding this "100% false"?

If you disable it, your log files would increase. So how is that not saving you resources having it enabled?

Or maybe you're seeing something I am not here?

OK, I guess "technically" it is correct in that it saves Apache resources from managing lots of large log files. However, the system Apache is running on is still using resources to manage the log files. Especially when there's almost 700k files in the directory. It's just moving the resource usage from one place to another.