Summary:Cvs client server

This worked for me , i used both wincvs as well as smart cvs ,i was struck 
at auth level.
You need to setup the cvs in inetd. The wincvs can communicate to the cvs
server.
Thanks to every body.
Some thing like this.

/etc/services :
cvspserver 2401/tcp
/etc/inetd.conf :
cvspserver stream tcp nowait root /usr/local/bin/cvs cvs
--allow-root=/home/group/CVS pserver


From: Min Oo Tint <min@psde.mec.mei.co.jp>
To: "'RaghuNath L(Raghu)'" <LRaghuNath@Lucent.Com>
Subject: RE: Cvs client server
Date: Thu, 20 Jun 2002 13:47:24 +0100
Importance: high
X-Mailer: Internet Mail Service (5.5.2653.19)


sure, not ment sent many e-mail, too much on my mind
and forgotten to add few extra, hence overwhelming response
CVS manual from cvs.org explained it all and we have
is runiing here without any problem with smartCVS.
glad I could help
-----Original Message-----
From: RaghuNath L(Raghu) [mailto:LRaghuNath@Lucent.Com]
Sent: Thursday, June 20, 2002 1:21 PM
To: Min Oo Tint
Subject: RE: Cvs client server
Importance: High

Thanks lot for your overwhelming response .
At 01:23 PM 6/20/2002 +0100, Min Oo Tint wrote:
 >also read section 2.9.3.1 Setting up the server for password authentication
 >
 >from CVS manual
 >
 >
 >2.9.3.2 Using the client with password authentication
 >To run a cvs command on a remote repository via the password-authenticating
 >server,
 >one specifies the pserver protocol, optional username, repository host, an
 >optional port
 >number, and path to the repository. For example:
 >cvs -d :pserver:faun.example.org:/usr/local/cvsroot checkout someproj
 >or
 >CVSROOT=:pserver:bach@faun.example.org:2401/usr/local/cvsroot
 >cvs checkout someproj
 >However, unless you're connecting to a public-access repository (i.e., one
 >where that
 >username doesn't require a password), you'll need to supply a password or
 >log in first.
 >Logging in verifies your password with the repository and stores it in a
 >file. It's done with
 >the login command, which will prompt you interactively for the password if
 >you didn't
 >supply one as part of $CVSROOT:
 >cvs -d :pserver:bach@faun.example.org:/usr/local/cvsroot login
 >CVS password:
 >or
 >24 CVS-Concurrent Versions System v1.11.1p1
 >cvs -d :pserver:bach:p4ss30rd@faun.example.org:/usr/local/cvsroot login
 >After you enter the password, cvs verifies it with the server. If the
 >verification succeeds,
 >then that combination of username, host, repository, and password is
 >permanently
 >recorded, so future transactions with that repository won't require you to
 >run cvs login.
 >(If verification fails, cvs will exit complaining that the password was
 >incorrect, and nothing
 >will be recorded.)
 >The records are stored, by default, in the file '$HOME/.cvspass'. That
 >file's format
 >is human-readable, and to a degree human-editable, but note that the
 >passwords are not
 >stored in cleartext-they are trivially encoded to protect them from
 >"innocent" compromise
 >(i.e., inadvertent viewing by a system administrator or other non-malicious
 >person).
 >You can change the default location of this file by setting the
CVS_PASSFILE
 >environment
 >variable. If you use this variable, make sure you set it before cvs login
is
 >run. If you were
 >to set it after running cvs login, then later cvs commands would be unable
 >to look up the
 >password for transmission to the server.
 >Once you have logged in, all cvs commands using that remote repository and
 >username
 >will authenticate with the stored password. So, for example
 >cvs -d :pserver:bach@faun.example.org:/usr/local/cvsroot checkout foo
 >should just work (unless the password changes on the server side, in which
 >case you'll
 >have to re-run cvs login).
 >Note that if the ':pserver:' were not present in the repository
 >specification, cvs would
 >assume it should use rsh to connect with the server instead (see Section
 >2.9.2 [Connecting
 >via rsh], page 20).
 >Of course, once you have a working copy checked out and are running cvs
 >commands
 >from within it, there is no longer any need to specify the repository
 >explicitly, because cvs
 >can deduce the repository from the working copy's 'CVS' subdirectory.
 >The password for a given remote repository can be removed from the
 >CVS_PASSFILE by
 >using the cvs logout command.
 >
 >
 >-----Original Message-----
 >From: Min Oo Tint
 >Sent: Thursday, June 20, 2002 1:15 PM
 >To: 'RaghuNath L(Raghu)'
 >Subject: RE: Cvs client server
 >Importance: High
 >
 >
 >Hi,
 >
 >For windows client I used SmartCVS which uses network password
 >on unix for authentication - I think wincvs will be similar.
 >
 >On the UNIX side you need to read the attachment, it will help you set it
up
 >
 >
 >Hopes this help
 >
 >-----Original Message-----
 >From: RaghuNath L(Raghu) [mailto:LRaghuNath@Lucent.Com]
 >Sent: Thursday, June 20, 2002 12:43 PM
 >To: sunmanagers@sunmanagers.org
 >Subject: Cvs client server
 >
 >
 >Hello Managers,
 >This may be an off topic question.
 >
 >Does any body have setup Unix cvs server and Windows client ?
 >I have unix server ready with cvs repository
 >2) samba is running on it
 >3)wincvs is installed on NT2000 hosts
 >4)Phyton and tcl is installed
 >
 >All iwan't know is how to make wincvs to talk to unix cvs server.
 >I tried .rhosts,nt server .
 >Please help i will summarize.






At 01:21 PM 6/20/2002 +0100, you wrote:
>Hi,
>
>forgotten
>
>you need to add following to your /etc/services
>
>cvspserver      2401/tcp
>
>Regards,
>
>
>Min Oo Tint
>
>Panasonic System LSI Design Europe (PSDE)
>A Division of Matsushita Electric Europe (HQ) Ltd.
>  <<Min  Oo Tint.vcf>>
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers