Re: Any reason to open access logs in parent on Windows?

[Eric Covener]

On Tue, Sep 23, 2014 at 4:33 PM, Jeff Trawick <traw...@gmail.com> wrote:

> Better error reporting if file/pipe fails?  Maybe  (abort startup if
> error-prone piped logger config is bad?). This would need to be tested with
> a bad config to check for exit+restart loop.


​Tried a few cases on the access log.  A quickly exiting rotatelogs (bad
option) is not handled either way (loops with usage() printed to error log)
and a bad executable path is handled well both ways. When it's opened in
the child only, the parent pops out of WaitForMultipleObjects() when the
child exits.  Configtest doesn't hit any of it.