[gdal-dev] VSI issue

Ari Jolma ari.jolma at gmail.com
Sun Nov 20 04:04:50 EST 2011

On 11/19/2011 04:24 PM, Even Rouault wrote:
>> I found the problem. It is changeset 23022 (by you, Even :), which
>> removes support for "stdout" and adds "/dev/stdout" as an alias to
>> "/vsistdout/". Simple, but took me a while to find out especially as the
>> log message begins "mentions in the doc".
> Hum, so it means that under your CGI the stdout file is actually closed.
> Because before r23022 /dev/stdout was considered as a regular file and was
> opened, but now that /vsistdout/ is used, it directly writes to FILE* stdout.
> I don't know Apache but perhaps there's an option to leave stdout opened for
> the forked process ?

I think the correct thing to do is to use "/vsistdout/" in CGI programs,
since it works both in older (1.8.0) and newer GDAL (next release).


More information about the gdal-dev mailing list