Re: Possible Spam: Re: CVS and SSH V2
Guys Finally got it all working! woho! Only question I have left is can you make files read only in smartCVS so that users have to select the file for editing first, to stop other users being able to edit the same file at the same time? Thanks for all the help! ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Russ Sherk wrote: >I think you can put the port into CVS_RSH. Here is mine on winXP using plink: > >Z:\>echo %CVS_RSH% >"d:\Tools\plink.exe" -ssh -pw "xx" >Z:\>echo %CVSROOT% >:ext:[EMAIL PROTECTED]:/var/cvs >--- >Does this not work on linux? > > No. It's an implementation difference. The src/run.c piped_child function accepts an argv array as an argument on Linux and passes that argv directly to execvp. Since argv[0] holds the contents of $CVS_RSH, the system looks for a process names "$CVS_RSH", spaces, arguments, and all. The windows-NT/run.c pipted_child function turns it's argv into a single string with space-delimited arguments which it then passes back to the Windows shell for parsing, so the contents of $CVS_RSH gets resplit on spaces. Regards, Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
On 7/6/05, Derek Price <[EMAIL PROTECTED]> wrote: > Derek Price wrote: > > >Also, specifying a port number to the :ext: method will be ignored at > >best. (it wouldn't be hard to add support for it, but no one has done so). > > > > > > Excuse me - it would be hard to do in a general way using the current > CVSROOT conventions since the -p option is not supported by rsh, only > ssh. At least, then specifying a port for rsh would no longer be > ignored but would probably cause errors. > > You can stuff the port number into an ssh wrapper script or into your > ~/.ssh/config file for the CVS server if you need to. Trying to stuff > it into CVS_RSH will break, though adding support for this shouldn't be I think you can put the port into CVS_RSH. Here is mine on winXP using plink: Z:\>echo %CVS_RSH% "d:\Tools\plink.exe" -ssh -pw "xx" Z:\>echo %CVSROOT% :ext:[EMAIL PROTECTED]:/var/cvs --- Does this not work on linux? I don't use the port (-P for plink) but the other optons work fine. > too hard using the GNULIB argument parsing module (argv? argz? > command-line? something like that), at least on feature, if anyone > wanted to write and submit a patch. > > Cheers, > > Derek > > > > ___ > Info-cvs mailing list > Info-cvs@gnu.org > http://lists.gnu.org/mailman/listinfo/info-cvs > --Russ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Guys finally seem to have got the cvs command to work, by creating a symbolic link from the /usr/bin to the cvs within usr/local/bin, which is not loaded on ssh scripts However, when i go to checkout i now get the following error message: cvs -d :ext:[EMAIL PROTECTED]:/appl/cvs checkout -P ole (in directory C:\) cvs checkout: in directory ole: cvs checkout: cannot open CVS/Entries for reading: No such file or directory cvs checkout: Updating ole cvs [checkout aborted]: could not chdir to ole/Application: No such file or directory As far as I can see there is a CVS directory and and entries within that all belonging to user gtx. Any ideas why this is? p.s should my root be set to the directory that contains the directory CVSROOT? Thanks for all the help ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Matt Doar wrote: >Derek, > >From the CVS manual, I see CVSROOT is indeed specified as: > >[:method:][[user][:[EMAIL PROTECTED]:[port]]/path/to/repository > > You specified a colon *after* the port field: Matt Doar wrote: >I believe you have to use: > >:ext:[EMAIL PROTECTED]:22:/appl/cvs/ole > > This is not allowed in the spec and I know of no clients that accept a colon there. Cheers, Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Possible Spam: Re: CVS and SSH V2
Got it: no colon allowed after a port number, and the colon between hostname and the repository path is optional. Exactly what the manual says. I'll go and get more coffee now ;-) ~Matt > -Original Message- > From: Derek Price [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 06, 2005 9:59 AM > To: Matt Doar > Cc: Todd Denniston; Liquidchild; info-cvs@gnu.org > Subject: Re: Possible Spam: Re: CVS and SSH V2 > > Matt Doar wrote: > > >Derek, > > > >From the CVS manual, I see CVSROOT is indeed specified as: > > > >[:method:][[user][:[EMAIL PROTECTED]:[port]]/path/to/repository > > > > > > You specified a colon *after* the port field: > > Matt Doar wrote: > > > >I believe you have to use: > > > >:ext:[EMAIL PROTECTED]:22:/appl/cvs/ole > > > > > > This is not allowed in the spec and I know of no clients that accept a > colon there. > > Cheers, > > Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Possible Spam: Re: CVS and SSH V2
Derek, >From the CVS manual, I see CVSROOT is indeed specified as: [:method:][[user][:[EMAIL PROTECTED]:[port]]/path/to/repository as you say, without the colon between the hostname and the repository path. However, SmartCVS does add a colon when putting the various fields together to create a CVSROOT. The relevant changes in ChangeLog around 2000/10/17 and parse_cvsroot() in src/root.c in 1.12.9 suggest that the extra colon is still allowed. Is it in fact deprecated? ~Matt > -Original Message- > From: Derek Price [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 06, 2005 9:02 AM > To: Matt Doar > Cc: Todd Denniston; Liquidchild; info-cvs@gnu.org > Subject: Re: Possible Spam: Re: CVS and SSH V2 > > Matt Doar wrote: > > >>>:ext:[EMAIL PROTECTED]:22\appl\cvs\ole > >>> > >>> > > > >I believe you have to use: > > > >:ext:[EMAIL PROTECTED]:22:/appl/cvs/ole > > > > > > You are correct about the forward slashes, but not the extra colon. > Also, specifying a port number to the :ext: method will be ignored at > best. (it wouldn't be hard to add support for it, but no one has done > so). > > Cheers, > > Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Derek Price wrote: >Also, specifying a port number to the :ext: method will be ignored at >best. (it wouldn't be hard to add support for it, but no one has done so). > > Excuse me - it would be hard to do in a general way using the current CVSROOT conventions since the -p option is not supported by rsh, only ssh. At least, then specifying a port for rsh would no longer be ignored but would probably cause errors. You can stuff the port number into an ssh wrapper script or into your ~/.ssh/config file for the CVS server if you need to. Trying to stuff it into CVS_RSH will break, though adding support for this shouldn't be too hard using the GNULIB argument parsing module (argv? argz? command-line? something like that), at least on feature, if anyone wanted to write and submit a patch. Cheers, Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Matt Doar wrote: >>>:ext:[EMAIL PROTECTED]:22\appl\cvs\ole >>> >>> > >I believe you have to use: > >:ext:[EMAIL PROTECTED]:22:/appl/cvs/ole > > You are correct about the forward slashes, but not the extra colon. Also, specifying a port number to the :ext: method will be ignored at best. (it wouldn't be hard to add support for it, but no one has done so). Cheers, Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Possible Spam: Re: CVS and SSH V2
> > :ext:[EMAIL PROTECTED]:22\appl\cvs\ole I believe you have to use: :ext:[EMAIL PROTECTED]:22:/appl/cvs/ole as the CVSROOT format (note extra colon and forward slashes). If you are using the professional version of SmartCVS, it will generate the ssh keys for you, which can be convenient. ~Matt > -Original Message- > From: [EMAIL PROTECTED] [mailto:info-cvs- > [EMAIL PROTECTED] On Behalf Of Todd Denniston > Sent: Wednesday, July 06, 2005 6:47 AM > To: Liquidchild > Cc: info-cvs@gnu.org > Subject: Possible Spam: Re: CVS and SSH V2 > > Liquidchild wrote: > > > > Guys, > > > > I am trying to setup CVS and SmartCVS to allow communication with each > > other. > > > > smartcvs has a mailing list which might help more. > http://www.smartcvs.com/smartcvs/community.html > > > I did not set up the CVS server, our admin team has done that. So here > > is what i have been doing: > > > > I have installed SmartCVS and entered the following into for the > > connection string: > > > > :ext:[EMAIL PROTECTED]:22\appl\cvs\ole > > > > using public/private key auth, with the private key file pointed to and > > the public copied into authorized_keys. When I test the connection > > using smart cvs it seems fine, then when i click next to enter a > > modules i get an "io error with details null". > > > > with regular cvs the troubleshooting starts with: > https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_21.html#SEC189 > in your case I think the command you want to try is something like: > ssh [EMAIL PROTECTED] "cvs -v" > or > ssh -l gtx 10.10.115.11 "cvs -v" > > > I am really hitting a brick wall with this stuff I have never had to > > setup CVS with SSH before, I have even tried previous clients of WinCVS > > and get similiar setup, again I seem to be able to login to the server, > > as its return command ran with 0, but when i try to checkout the module > > i get a "ksh: cvs not found error" > > This looks like the environment of the server does not know where to find > the cvs executable, you might try smartcvs's equivalent of defining > CVS_SERVER giving it the full path the the cvs executable the admin staff > want you to use. > > > > > This would imply its not loading the enviroment variables hences cvs is > > not on the path, which i think it does not do for ssh, ie does not load > > the .profile, but how do you get round this. If indeed this is (a) > > problem. > > you could try this (assuming the server is running a shell that accepts > bash > scripts): > ssh [EMAIL PROTECTED] "echo $PATH" > ssh [EMAIL PROTECTED] ". /etc/profile;. ~/.profile;echo $PATH" > ssh [EMAIL PROTECTED] ". /etc/profile;. ~/.profile;cvs -v" > > > > > I am unsure if i am required to do anything on the client machine > > either, i.e set any enviroment variables. > > > > As you can see any help would be appreciated, and if anyone has done > > this before i would very much like to talk to them! > Please keep responses to me on the mailing list, thanks. > > This is not intended to be direction to a gov contractor to do anything, > just a listing of information which _may_ answer the question which was > asked. > -- > Todd Denniston > Crane Division, Naval Surface Warfare Center (NSWC Crane) > Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
