On 27 Dec 2001 at 16:32, Binand Raj S. wrote:
> service cvspserver
> {
> socket_type = stream
> protocol = tcp
> wait = no
> user = root
> server = /usr/bin/cvs
> env = HOME=/usr/local/cvsroot
> server_args = --allow-root=/usr/local/cvsroot/myproject pserver
> disable = no
> }
Additionally create .rhosts file in each users home dir. which contains pairs
of remote logging info. It includes ip address and user name separated by
space.
My .rhosts reads as
[shridhar@perth shridhar]$ cat .rhosts
192.168.7.161 shridhar
192.168.6.178 shridhar
[shridhar@perth shridhar]$
Enable rsh as xinetd service and change /etc/hosts.[allow/deny] appropriately..
Now windows clients can also use cvs. Just configure wincvs to use .rhosts
authentication..
>
> Now you are all set. Give out to users that their cvsroot is
> :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot/myproject
Use CVSROOT environment varible. Make life easy..;-)
>
> PPS: CVS is not yet PAM-aware. So, every developer will need a login
> on your cvs server. You have to evaluate the implications of this. A
> rewrite of CVS's network code that is PAM aware is available on
> http://cvs-nserver.sourceforge.net - you can try that also.
CVS can use a third program to authenticate users rather than using system
login. You need to tweak configuration for that. In addition to that you can
use readers/writers files in $CVSROOT/CVSROOT dir. This dir. stores
configuration for cvs.
Never tried third party authentication and readers/writers but should work.
CVS is pretty flexible so use.
Excellent HOWTO Binand. Adding it to my collection... I feel like posting CVS
administratoras guide. I don't know why you need a login at cvshome.org, just
to read it. That book contains all such tricks..
Shridhar
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
