[cvsnt] loginfo - need information

[Bo Berglund]

Make sure you are using the latest 2.0.62 (build 1874)
There have been a number of script handling problems in earlier builds.
Also note that from 2.0.62 the paths used in the script files must *not*
use the \ character, use / instead. So you have to change like this:

DEFAULT C:\Somepath\Someprogram.exe
to
DEFAULT C:/Somepath/Someprogram.exe

/Bo

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Vanier, Alexandre
Sent: den 16 februari 2005 16:18
To: cvsnt at cvsnt.org
Subject: [cvsnt] loginfo - need information


Greetings!

We are doing our migration of CVSNT 2.0.8 to 2.0.62 (on Windows server
2000) and we are almost finished!  Weeee.  Well, we do have some
problems but we are getting through one at the time.  One of the last
problem left that is still bugging me is the script to run in the
loginfo file under the CVSROOT folder.  On our old server (running
2.0.8) we currently have this line configured in the loginfo file:

DEFAULT (echo %s) >> \\OLD-SERVER\cvs_logs\CommitLog.txt

Of course putting that line in our loginfo file on the new server gave
us a couple of problems with the escape character.  Fine, I can write
the script a little bit differently, here's what we put in our loginfo
file on our 2.0.62 CVSNT server:

DEFAULT (echo %s) >> cvs_logs/CommitLog.txt

When we create a new project, the project will be created but we will
get an error because the script is not able to run properly : 

Script execution failed - path of the new project
cvs.exe add: warning: unrecognized response - script execution failed -
path of the new project.

We tried a couple of different variations for the line to configure in
the loginfo file and we always get this error message.  Has the standard
for the loginfo changed or are we just to ignorant to see what is
missing in the loginfo file for running a simple echo command that will
put the result in a txt file?  Even trying to run a simple dir of the
drive (from the loginfo) and putting the results in a txt file give us
the same error message.  We don't have any permission problem so far,
all folders got everyone full access at the moment (repository and the
direcotry of the logs).

Any advices or suggestions?

Thx!

Alex Vanier
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt