Thank you for your idea. But running logrotate on an "as needed" basis is just as much a nuisance as restarting apache. During a debugging session, I may want to clear the error.log file every 10 minutes -- Stephen On 16-04-04 06:08 PM, Alvin Starr wrote:
logrotate is your friend.
A well configured logrotate will get around most of those problems.
On 04/04/2016 06:01 PM, Stephen wrote:
I have Apache running on my system for web development with php.
Apache writes to an error.log file unique for the specific web site that I am working on.
During debugging the log file grows, and I like to clear it every now and then.
I had to change ownership of the file to me. I five read/write to everyone.
But when I truncate the file and save, Apache no longer writes to it. The Apache error logs do not indicate a problem.
I restart Apache and all is good again. But this is a nuisance.
Is there a way to avoid this nuisance?
Thanks