G’Day

I have a problem to connect to cvsroot directory... the local
directory works right, but if I want to connect to the maped drive I
always become this fault…


C:\>set cvsroot=:pserver:votumu@ras1:c:/data/cvsrepo/test_local

C:\>cvs login
Logging in to :pserver:votumu@ras1:2401:c:/data/cvsrepo/test_local
CVS password: ******

C:\>cvs logout
Logging out of :pserver:votumu@ras1:2401:c:/data/cvsrepo/test_local

C:\>set cvsroot=:pserver:votum@ras1:m:/data/cvs/test

C:\>cvs login
Logging in to :pserver:votum@ras1:2401:m:/data/cvs/test
CVS password: ******
cvs [login aborted]: unrecognized auth response from ras1: cvs server:
E cannot
open m:/data/cvs/test/CVSROOT/config: Permission denied

C:\>

---

Request for Question Clarification by maniac-ga on 12 Feb 2003 18:00 PST

Hello Stahlone,

Let me confirm your set up and ask a short question:

  Client  --  ras1 (CVS server)  -- [some machine with "m" drive
mapped]

and the user votum (and votumu) has an account on the ras1 system.
Please confirm this (or correct).

When you login to ras1 directly as votum, and access the directories
on the "m" drive, what does Windows show for file and directory
protections?  At a minimum, you will need read / write access to the
CVS directories to update the log files, perform check out, check in,
etc.

However, I have also found some sites (messages in 2000, 2001)
indicating that performance to a networked drive is either "awful" or
"not supported", and a local drive should be used. You may have to
"solve" this problem by running the pserver on the machine with the
"m" drive.

  --Maniac

---

Request for Question Clarification by maniac-ga on 19 Feb 2003 16:28 PST

Hello Stahlone,

Are you still interested in a solution for this problem or have you
fixed it with the information already provided?

  --Maniac