[cvsnt] Problems with CVSNT in combination with CVSMailer ->Nothing happens

[Iwan]

Thanks, this pointed me in the right direction. As it is, I had a CVS
1.11 version on my path that was executed when I did a checkout. So I
deleted that, which resulted in the right CVS to be called, the actual
one that came with WinCVS in my case. Now I got an access-denied error,
which was fixed by granting the right user on the Win2K server that has
CVSNT and CVSMailer running. After setting the right permissions on the
log directory, the log directory is being filled with logs.

Now it all works excellently.

Thanks again,
Iwan

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Tony Hoyle
Sent: Friday, April 18, 2003 8:37 PM
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Problems with CVSNT in combination with CVSMailer
->Nothing happens


Bo Berglund wrote:

 
> Does someone have a clue as to why the loginfo line will *not* result 
> in execution when he commits his changes????
> 
This is suspicious:

        cvs login: CVSROOT requires a path spec:
        cvs login:
:(gserver|kserver|pserver):[[user][:password]@]host[:[port]]/path
        cvs login: [:(ext|server):][[user]@]host[:]/path

is exactly what a cvs 1.11.x client will print when it's invoked from
the command line with a DOS path in the CVSROOT, so there's more than
one client on the machine, which won't help things (especially if it
gets invoked accidentally by the service).

'The current directory is invalid' tends to get printed when things like
UNC paths are used - where are the repository & temp actually located?
- It's printed by cmd.exe when it can't start up because you're trying
to run it somewhere that doesn't actually exist.  The '-t' output is
pretty verbose at this point and will usually tell you exactly what the
problem is.

Tony

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