[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Confusion regarding pserver to extssh switch.

From: Rick Genter
Subject: RE: Confusion regarding pserver to extssh switch.
Date: Fri, 7 Oct 2005 07:51:02 -0700

From: address@hidden [mailto:address@hidden On Behalf Of Shaun T. Erickson
Sent: Friday, October 07, 2005 10:46 AM
To: info-cvs
Subject: Re: Confusion regarding pserver to extssh switch.

On 10/7/05, Shaun T. Erickson <address@hidden> wrote:

On 10/5/05, Mark D. Baushke <address@hidden > wrote:
> >
> > :pserver: is a completely separate execution path from using :ext: (or
> > :extssh:).

Ok. So I turned off pserver, removed the passwd file it used, made sure I have an account on the server that I can ssh to, made sure I was in the cvs group and that the repository has 770 plus setgid permissions, and that my account is able to write into it. On another linux box, where I'd been testing the previous (and working) pserver connection, I removed the .cvspass file, and verified that I can, indeed log into the other machine via ssh.

I made sure that CVS_RSH is set to ssh and that I changed pserver to ext in the CVSROOT variable, which is set to:


When I try to do a cvs update however, I get:

cvs [update aborted]: connect to failed: Connection refused

Why is it still trying to access pserver? Shouldn't it just be ssh'ing into spot and then issuing cvs commands?

Sorry to follow-up my own post, but I just discovered that 'cvs update' fails, while 'cvs -d :ext:address@hidden:/home/cvs update' works. So the question now, is, why won't the short version work?
Because the old CVSROOT string is stored in the CVS/Root files in your sandbox. You need to either remove your sandbox and checkout a fresh one, or manually edit the CVS/Root files in your existing sandbox to use the new CVSROOT string.

Rick Genter
Principal Engineer
Silverlink Communications
(781) 272-3080 x242



reply via email to

[Prev in Thread] Current Thread [Next in Thread]