[gdal-dev] VSI issue
even.rouault at mines-paris.org
Sun Nov 20 05:50:10 EST 2011
Le dimanche 20 novembre 2011 10:04:50, Ari Jolma a écrit :
> 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).
Hum, I'm lost. In your first message, you write that using "/dev/stdout" no
longer works with trunk. But since r23022, "/dev/stdout" is redirected to
"/vsistdout/", which works. Sounds like there is a contradiction somewhere.
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
More information about the gdal-dev