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.
Thanks for the info Bo.
I think I wasn't quite clear in my previous post. CVSMailer is seeing the
command line correctly. The emails sent out by CVSMailer have the correct
links. Looking at the log files, I also see the module folder in Parameter
5.
The problem that I have is that my vbs script is missing the first argument
of the module folder. The only argument that I get in my script is the
filename and the pre and post commit revision numbers. Commenting out the
triggering of CVSMailer seems to solve this.
Previously I had CVSNT 2.0.51d working with CVSMailer 1.5.1.31. When I
upgraded CVSNT to 2.5.01.1976 without upgrading CVSMailer, I get error
messages. These error message appear before the output from my script in the
status window of WinCVS. When I upgraded CVSMailer to 1.5.2.41, these error
messages disappear. My loginfo file was not changed during the upgrade.
Well, it was changed to correct the slashes to make version 1.5.2.41 work.
>From that, I gather that CVSMailer is actually executed before my script is
executed. As such, I was wondering if CVSMailer could have altered the
command line arguments passed to my script. Or is it something with CVSNT?
How Hon.
"Bo Berglund" <Bo.Berglund at system3r.se> wrote in message
news:mailman.5.1119261531.9754.cvsnt at cvsnt.org...
What CVSMailer sees on teh command line can be checked in the logfile it
creates.
Switch on debug logging in the ini file and try again.
Now in the ML<date>.log file you will see exactly what was passed to
the program on the command line.
Example:
20050620 01:18:20 DEBUG: Root read from ini file = 3RProj
20050620 01:18:20 DEBUG: Parameter 1: -l0000069c <= this is the -l switch
and the PID
20050620 01:18:20 DEBUG: Parameter 2: bob <= $USER expands to this
20050620 01:18:20 DEBUG: Parameter 3: /3RProj <= $CVSROOT expands to
this
20050620 01:18:20 DEBUG: Parameter 4: ADM/FrameWorkCenter
WORKCTR.dpr,1.46,1.47 <= Module folder + list of committed files
/Bo
-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Ho How Hon
Sent: den 20 juni 2005 08:51
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Problem with Loginfo???
Hi,
I have been seeing some inconsistencies with loginfo. Here's my setup.
Server:
Win2k server
CVSNT ver 2.5.1.1076
CVSMailer ver 1.5.2.41
Client:
WinXP Pro
WInCVS 2.0.0.2
My loginfo script on the server is setup as follows:
ALL cscript.exe D:/CVS/cvsrepo/test/CVSROOT/logbugdata.vbs "%{sVv}"
ALL C:/Programs/CVSMailer/CVSMailer.exe -l$CVSPID $USER $CVSROOT -rcvs_test
%{sVv}
When I commit a file, I find that my vbs script is only able to see one
argument from the command line. The argument is the name of the file that is
being committed and the previous and current revision number.
Now I modify my loginfo file as such:
ALL cscript.exe D:/CVS/cvsrepo/test/CVSROOT/logbugdata.vbs "%{sVv}"
#ALL C:/Programs/CVSMailer/CVSMailer.exe -l$CVSPID $USER $CVSROOT -rcvs_test
%{sVv}
In this case, when I commit a file, I do not get any email notification as
expected. This time, my vbs script is able to see 2 arguments from the
command line. The first argument is the repository subdirectory and the
second argument is the name of the file that is being committed and the
previous and current revision number.
Has anyone else encountered this? Is this a bug with CVSNT or CVSMailer or
am I doing something wrong?
How Hon
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs