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

Gerhard Stegemann GStegemann at csi.com
Fri Aug 23 20:14:42 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.


"Boyd Meier" <bmeier at acornsys.com> schrieb im Newsbeitrag
news:mailman.1030128006.706.cvsnt at cvsnt.org...

> 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.

I've also heard from such a flag. But I also don't know its name and how it

> 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}

Yes, that should do trick. Thanks.

> 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.

That's quite possible. I will check this again.

> 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.

OK, but are there any hints how to make it work or somehow compatible?

Gerhard Stegemann

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