Hi Mladen, Aaah, OK, so I was always talking about Apache and you about IIS. That explains our different observations.
If we don't find a solution making line endings work for IIS/Sun/Apache und Cygwin, we could also add the platform information to the jk_logger_t or it's logger_private and use this info in jk_log to determine the correct line endings. To make it perform, we could actually put the line ending and it's size into the jk_logger_t or it's private. Concerning apache 1.3: I did the same kind of build with 1.2.21 and 1.2.20 and got the same negative result (httpd opening the log file but writing all log output to stdout/stderr and to the error log). But: using your official build for 1.2.20 logging worked normally! So that problem seems to be related to my build, but I've got no idea what's wrong with my build. I built against an installed form of the official download apache_1.3.37-win32-x86-src.msi. Regards, Rainer Mladen Turk schrieb: > Rainer Jung wrote: >> Hi Mladen, >> >> I think we don't use stdio. APR has apr_file_open() which uses >> CreateFile() and apr_file_write() which goes back to WriteFile() on >> Windows. >> > > We are using stdio for other web servers, so if you add CRLF then > the IIS will be broken. Perhaps opening the files as binary for > windows, and then forcing CRLF will do. However this would break > cygwin builds thought. > > I'll check 1.3 tomorrow. > > Regards, > Mladen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
