Hi!

Thanks for helping out. Your suggested solution looks reasonable, but I uses
the ms4w binary distribution to perform the tests and I haven't set up any
compiling environment at the moment. A colleague of mine is doing the
compiling on our Linux systems, but he is on vacation for another week. I'll
have to wait for him to return to work before doing any compiling.

Regards,
Pål Kristensen


Daniel Morissette-2 wrote:
> 
> Maybe a fflush() on the msDebug() output at the end of each FastCGI 
> request would help? For a test, please try adding one in the msDebug() 
> function in mapdebug.c and see if that helps:
> 
> --- mapdebug.c  (revision 7902)
> +++ mapdebug.c  (working copy)
> @@ -361,6 +361,7 @@
>           va_start(args, pszFormat);
>           msIO_vfprintf(debuginfo->fp, pszFormat, args);
>           va_end(args);
> +        fflush(debuginfo->fp);
>       }
>   #ifdef _WIN32
>       else if (debuginfo->debug_mode == MS_DEBUGMODE_WINDOWSDEBUG)
> 
> 
> If that helps then please file a ticket and assign to me (Trac id 
> dmorissette). The final solution will NOT be to call fflush() all the 
> time as in the above gtest, but to create a new msDebugFlush() function 
> that is called once at the end of each FastCGI request
> 
> Daniel
> -- 
> Daniel Morissette
> http://www.mapgears.com/
> _______________________________________________
> mapserver-users mailing list
> [email protected]
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/FastCGI-and-trouble-writing-to-the-MS_ERRORFILE-tp19413175p19428577.html
Sent from the Mapserver - User mailing list archive at Nabble.com.

_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Reply via email to