Antony
Mon Feb 07 05:51:18 CST 2005
Hi
My understanding was based on reading up on Perl, that PWD was setup by the
webserver for CGI programs to identify where they were running. However
running a simply C++ program shows that no such variable was setup so i
guess that was wrong. So there was a little misunderstanding as to the
symptoms, but the problem remains the same. Running the simple test program
and getting it output its current working directory (using getcwd) has shown
that its being run in two different location between IIS running on the two
OSs. On the W2K server its still reports running in the webroot even though
its located in a subdirectory called cgi-bin. Yet on Win XP Pro its reports
running from the cgi-bin subdirectory. So it would be helpful if someone
could point out where the change occured to where CGI programs were being
run from. I wonder if this is another side effect of running IIS from the
Pro rather than Server version of an OS?
Thanks
Tony
"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:xn0dy51hs98ran6018@news.microsoft.com...
> Hi,
>
> I cannot recognise any PWD environment variable related to IIS. Isn't this
> something that is specific for Perl?
>
>
> --
> Regards,
> Kristofer Gafvert
> www.gafvert.info - My Articles and help
> www.ilopia.com
>
>
> Antony Scerri wrote:
>
>> Hi
>>
>> I use a cgi-bin counter script written in Perl to provide graphical
> counters
>> on my site. Part of this relies on writing to a private directory not
>> accesible on the web server. The script was located at
>>
http://www.website.com/cgi-bin/counter.pl and it used to simply have the
> path
>> to write in as "../private/xxx" under IIS on Windows 2000 advanced server
>> this used to result in going down one directory from the webroot as the
> PWD
>> environment variable was set to the webroot (not including the cgi-bin
> path
>> segment). Now under Windows XP Proffesional IIS is setting the PWD
>> environemtn variable to be the path including the cgi-bin directory. I am
>> using Active Perl on both machines.
>>
>> Does anyone know if this is a bug in the latest IIS, or where if any they
>> document this change in behaviour of IIS.
>>
>> Thanks
>>
>> Tony