[cvsnt] Commit continues after non-zero status from verifymsg

[Prochazka, Jan]

Stupid me ! of course: verifymsg.exe

> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On
Behalf
> Of Prochazka, Jan
> Sent: Wednesday, May 25, 2005 14:30
> To: cvsnt at cvsnt.org
> Subject: RE: [cvsnt] Commit continues after non-zero status from
verifymsg
> 
> My 2 Cents to this:
> We are running 2.0.58d (server and most of the clients) and it rejects
> commits fine on non zero return from our home grown veryfimsg.exe
> JP
> 
> > -----Original Message-----
> > From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On
> Behalf
> > Of Gary Brunton
> > Sent: Tuesday, May 24, 2005 17:19
> > To: cvsnt at cvsnt.org
> > Subject: [cvsnt] Commit continues after non-zero status from
verifymsg
> >
> > I've spent way too many hours on this issue to even tell you because
I
> > would be too embarrassed. I probably should have just given up along
> > time ago.
> >
> > I have tried cvsnt version's 2.5.01.1976, 2.5.02.1914, 2.0.62.1861,
> > 2.0.62.1974, 2.0.60, 2.0.59 and I can not get any of them to cancel
my
> > commit using the verifymsg method. But I have no problem getting it
to
> > work with cvsnt version 2.0.51d. This is the version that comes with
> > WinCVS version 2.0.0.2. I can't use that version though because of
> > other problems I'm having with that version.
> >
> > I've installed all of these cvsnt's on windows xp and I am
connecting
> > to cvsnt using the sspi protocol. The verifymsg file points to a
> > script that in its simplest form prints a test message to standard
> > output and exits with a 1.
> >
> > When I perform a commit I see my test message fine so I know that
the
> > script is running properly but the commit succeeds with a code of
> > zero.
> >
> > Again, using cvsnt version 2.0.51d the commit fails and returns code
1
> > just like it is supposed to.
> >
> > Has anyone else experienced this problem and found a solution.
> >
> > Please help.
> >
> > Thanks,
> > Gary
> >
> > >Has anyone else noticed this? I am also experiencing this problem.
> > >
> > >Gary
> > >
> > >>Hi
> > >>
> > >>I'm having the same issue described below with build 1927.  Is
this
> a
> > bug or is it supposed to >behave this way?
> > >>
> > >>Thanks
> > >>Mark Erdtmann
> > >>
> > >>> Hi,
> > >>>
> > >>> From version 2.5.01 a non-zero return status from a script in
> > verifymsg file does not stop the commit. Looking > in logmsg.cpp
> > learns that in do_verify the status of the call to run_trigger is
not
> > tested for a non-zero return. Is > this a bug or should the message
be
> > verified with another trigger (precommand?).
> > >>>
> > >>> Klaas Haasjes
> > _______________________________________________
> > cvsnt mailing list
> > cvsnt at cvsnt.org
> > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> >
> >
_____________________________________________________________________
> > This email has been scanned by the MessageLabs Email Security
System.


_____________________________________________________________________
This email message, including any attachments, may contain confidential and proprietary information for the sole use of the intended recipient.  If you are not the intended recipient, you are hereby notified that any use, copying or dissemination of this message is strictly prohibited.  If you received this message in error, please notify Brooks Automation, Inc. immediately by reply email or by calling Brooks US Headquarters at +1 978-262-2400. Then delete this message from your system, without making any copy or distribution.  Thank you.