[cvsnt] cvsnt 57g under Redhat 7.1 - some problems

Boyd Meier bmeier at acornsys.com
Fri Aug 23 19:39:43 BST 2002

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 don't know the answer to all of your questions, but here as a couple of
things I have noticed.

1) There is a preserve permissions configuration flag, but I'm not sure what
it does.  The scripts permissions are reset because the administrative
rebuild removes and rechecks out everything.

2) The loginfo and other trigger files need a valid executable as the first
token in the command due to the way that cvsnt runs them, so what I have
done is use a workaround like:
DEFAULT	bash $CVSROOT/CVSROOT/loggingscript %{sVv}

3) The lock file issue seems to have gone away for me when I fixed the
script issue.  Let me know if it does the same for you.

These problems are primarily due to differences between the cvsnt and
standard cvs in executing things on unix boxen.  In particular, the
run_popen functionality is different, causing most of the issues with
command execution that I have seen.


-----Original Message-----
From: cvsnt-admin at cvsnt.org [mailto:cvsnt-admin at cvsnt.org]On Behalf Of
Gerhard Stegemann
Sent: Friday, August 23, 2002 6:09 AM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] cvsnt 57g under Redhat 7.1 - some problems

I ran a few tests running cvsnt under Redhat 7.1.  Basically
to test a notification script.

I have installed the scripts (cvslog, cvsprep) in the CVSROOT
directory of repository, which didn't cause any problems.
But every time something is committed into the repositories
CVSROOT the execution permissions are removed by cvsnt.
Is this expected? Or is there a configuration parameter to
avoid this.

The two other problems are that a simple ALL clause in loginfo
containing some UNIX command always fails with "No such file or
directory". But all commands do exist. Are there any specific
requirements to execute UNIX on the path?

And also the server fails to remove a lock file. The path to the
lock file exists, but the lock file itself seems not to exist
anymore when the server attempts to remove it.

| E:\TEMP\CVSROOT>edit modules
| E:\TEMP\CVSROOT>cvs commit -m "Module mess added."
| cvs commit: Examining .
| Checking in modules;
| /devel/cvsroot/CVSROOT/modules,v  <--  modules
| new revision: 1.6; previous revision: 1.5
| done
| E cvs [server aborted]: cannot exec (echo ""; id; echo "CVSROOT
| ; date; cat) >> /devel/cvsroot/CVSROOT/commitlog: No such file or
| error
| cvs server: Rebuilding administrative file database
| cvs server: failed to remove lock dir /var/lock/cvs/CVSROOT/#cvs.lock: No
such file or directory

Are this specific cvsnt Linux problems?

Gerhard Stegemann

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

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook