[naviserver-devel] more logging problems on Windows

[Andrew P. <at...@pi...>]

On Windows, I see two additional problems with logging:

One, the access log file is opened and seems to get rolled/renamed
properly, but it is always empty, zero bytes!  No content ever seems
to make it into the access log file.

Two, calling ns_logroll crashed Naviserver with this error:

  Debug Assertion Failed!
  f:\dd\vctools\crt_bld\self_x86\crt\src\write.c
  Line:  68
  Expression:  (_osfile(fh) & FOPEN)

This is very hard to debug because it happens AFTER we've stopped
writing to the old error log file!

Is there some good way I can temporarily direct debug statements to a
different file (or the console, or whatever)?  Maybe something as
simple as NOT redirecting stderr to the error log, and instead letting
it keep going to the console?

-- 
Andrew Piskorski <at...@pi...>