https://issues.apache.org/bugzilla/show_bug.cgi?id=43502
--- Comment #9 from David Fraser <[email protected]> 2009-02-19 10:00:37 PST --- (In reply to comment #8) > It seems pretty odd to do this. If you have some process which is randomly > making your log directory unwritable outside of your control (or knowledge), > who is to say that the log directory isn't going to become unwritable between > when the testconfig hook runs, and startup completes? > The original use case for this was not someone making the log directory unwriteable, but someone (myself!) forgetting to add the directory referred to in the ErrorLog directive. I would then run configtest and since it said everything looked OK, thought I was good to go - but restarting the server would actually stop it dead. At least printing out a warning gives you a flag that that needs to be fixed. It needn't actually try writing to the files - just checking that their directories exist would be OK for me... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
