Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
On 13 Dec 2005 09:15:46 +0100, Oliver Koltermann
<okoltermann_deletethis_ at gmx.de> wrote:
>bo.berglund at system3r.se (Bo Berglund) writes:
>
>>> [...]
>> change to:
>> DEFAULT <path to>\perl.exe C:/Bugzilla_CVS_integ/aaa.pl %{sVv}
>
>Hello Bo,
>
>does this mean it is normal to use absolute path names in the script
>too? (See my earlier thread...) I wondered about using an absolute
>path instead of the $CVSROOT variable. I know you are
>scripting-experienced, so how does this look to you?
>
Yes, I believe that you must use real paths to some of the scripting
components, like Perl for instance. Remember that the CVSNT service is
running under the LOCALSERVICE account and that this has access only
to limited resources. For example it does not have permissions to go
out on the network. I also belive that the only environment it sees is
the System environment, so if one likes to use a construct like:
DEFAULT perl.exe myscript.pl
then one has to make sure that the path to perl is included in the
system path and if it is not then you have to restart the PC after
adding it, since LOCALSYSTEM will have started (and read the
environent) before your edit is done.
Also I think that file associations are not particularly well migrated
to the LOCALSERVICE account too, so this construct will fail:
DEFAULT myscript.pl
because of that.
I saw your comment about the CVSNT specific variables like $CVSROOT
and Tony's reply too. After that I tried to find a full list somewhere
of these variables but I gave up. It would be good to have them
collected in one single place with a description and the scope of
application. But I cannot do it....
/Bo Berglund