Re: Right Permissons !?

[Greg A. Woods]

[ On Thursday, September 27, 2001 at 15:24:05 (-0700), Chris Barker wrote: ]
> Subject: Re: Right Permissons !?
>
> After reading this mailing list for a day, that seems to be pretty
> clear. Unfortunately, while I'm sure the info is there in the manual,
> going through it to figure out how to set it up did not make thaqt
> clear. It's time for me to figure out how to use rsh instead. I'm right
> now reading the section: "Connecting with rsh", and I'm still somewhat
> confused.

Connecting with RSH is really trivial.  You just make sure that you can
do something like "rsh cvs.server.host date" (i.e. successfully run the
'date' command on the CVS server host) and then use the ":ext:" method
in your CVSROOT specification.  (The manual gives another slightly more
specific test that might be needed if you have a different user-id on
the server host, but hopefully you can avoid that.)

If you want to use SSH it's just about as easy.  Do the same test, but
with "ssh", then set CVS_RSH=ssh in your environment.  All the rest
works the same (i.e. with ":ext:" in your CVSROOT setting).

Any other issues are really specific to RSH or SSH themselves, such as
setting the path (or CVS_SERVER), etc.

> The remote users are running windows and WinCVS: can they use rsh? all
> the examples I see are for pserver. I'll keep RTFMing ...

I dunno about RSH on M$-Windoze -- there are nasty issues if you have
the wrong RSH/RSHd implementation(s).  But I do know that SSH works OK
with WinCVS.  The best instructions on setting up the WinCVS client for
SSH are probably those published by SourceForge.net.

> OK, and I did chmod g+s on all the directories, and set all of them to
> group cvs. It still doesn't work. A remote user on WinCVS adds a
> directory, puts a file in it and adds that, and all seems fine from
> there, but non of the other users get that new directory when they do an
> update.

You'll have to post some 'ls -la' listings of the relevant repository
directories, and document which users are members of which groups, etc.,
as well as show cut&paste commands and errors so that someone on the
list might be able to help.  Note that you can probably run CVS from the
command.com prompt on M$-Windoze and that might make it easier to show
us what's not working and what it says when it fails.

For Linux you might also want to specify the kernel version, filesystem
mount options, filesystem types, etc.  There are many variables!  ;-)
With *BSD the defaults are mostly "right" for CVS, but as Larry says
there can be issues on Linux.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <address@hidden>     <address@hidden>
Planix, Inc. <address@hidden>;   Secrets of the Weird <address@hidden>