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.
I did a lot of troubleshooting yesterday and discovered that the loginfo
script seems to be the culprit. The only uncommented line in the script is
the following:
DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
When uncommented, commits give the error message and nothing is logged to
the commitlog file (which does exist). I have also tried using absolute
pathnames for the binaries (/bin/echo, /usr/bin/id, etc) and for the
commitlog file, with no change. If I comment this line out, the error
message stops, but obviously there is still nothing logged to the log file.
FYI, this is running on RedHat 9.
Thanks for your help...
Brian
Tony Hoyle
<tony.hoyle at march
-hare.com> To
Sent by: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
cvsnt-bounces at cvs cc
nt.org
Subject
[cvsnt] Re: commit problem
10/05/2005 08:05
PM
bwhicks at aep.com wrote:
> Hi,
>
> I just upgraded from cvsnt-2.0.58 to cvsnt-2.5.02.2099 and when I do a
> commit I get an error message stating: "Exec failed: No such file or
> directory". This is the last message before a "Success" message appears.
It
> seems like everything is working, though. I thought at first that a
taginfo
> script (or something similar) was misbehaving, but that does not seem to
be
> the case. Does anybody have any suggestions?
Switch on server tracing in the control panel then run cvs -ttt to trace
what's happening. You should be able to find out which script is
failing. It sounds like postcommit or postcommand.
Tony
_______________________________________________
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