Re: Access problems with WinCVS-clients, when repository is installed on LAN drive

[Todd Denniston]

address@hidden wrote:
> Hello,
>
> I'd like to establish a repository on a local network drive. In my
> first try importing modules to the net drive I used the CVSROOT
> :local:G:\CVS. Then the error message

I assume that if you are working with other people in this repository that 
after you get it setup you will only access the repository through methods 
like: :ssh: :ext: :pserver: , because :local: or :fork: access to a network 
drive with CVS is a bad idea under any OS and any version of CVS.


> cvs [log aborted]: Local access to network share not supported (Use -N
> to override this error).
>
> came up. Neither in the options nor in the online manual of the
> WinCVS-Client I found anything about activating this -N option by
> default via the GUI. So I decided to use the :fork:-protocol. I was
> able to import my modules error free into the repository placed on the
> net drive G:\.

You are talking about the CVSNT version of CVS, their website and newsgroup 
will have better answers for the error (actually informative and very good 
advice) message. You would probably be best off never using that -N option to 
override it because multiple access to a network drive with :local: or :fork: 
with CVS is a bad idea under any OS and any version of CVS.

The CVSNT newsgroup is here:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.cvsnt



> Unfortunately, when checking out, updating or committing I get the
> following error statements (examples):
>
> a) with fork-protocol:
>
> > cvs -w -d :fork:G:\CVS checkout -P -- TTPowerPlant
>
> cvs server: connect to 127.0.0.1(127.0.0.1):2402 failed: Es konnte
> keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung
> verweigerte. (translated: unable to establish connection, target
> computer denies the connection)
>
> b) with local-protocol:
> I get the 1st above mentioned error message, that I should use -N
> command-option.
>
> The error advice to use the -N command-option helps to solve the
> problem, that's good. But the bad thing is that I can only achieve it
> using the command line. I'd like (and all the others developers here in
> the LAN) like to use the WinCVS-client. So my question is:
>
> How can do all the accessing command on the repository on the local
> network drive using the WinCVS-client, without having this mentioned
> problems?
>
> Thanks for your help
> Michael
>
>
> System description:
> -----------------------------------------
> WinCVS Version 2.0.2.4 (Build 4)
> CVSNT Version (Aug 19 2004)
> Repository established on LAN drive
> OS: WinXP Prof.
> Python 2.4.3 (#69, Apr 11 2006, 15:32:42)
>
> _______________________________________________
> info-cvs mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/info-cvs


--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter