
Signature
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>
On 03.03.2004 18:46, in article
macdev-861666.10463403032004@senator-bedfellow.mit.edu, "Miro Jurisic"
<macdev@meeroh.org> wrote:
>> You may want to consider that it is usually strongly recommended to never
>> use local mode of CVS: you will most likely end up with a corrupted
>> repository.
>
> Where did you get that?
Well, you can always search Google for "CVS local mode repository corrupt"
to get a ton of hits :). I think that I read this in one of the CVSNT
installation HOWTOs, which says "local: Should never be used by CVS clients
as accessing raw repository files will result in corrupt files and dangling
file locks": http://www.ypsolog.com/docs/comp/windows/cvsnt.html
Actually, this is quite obvious. If you expose your full repository to the
client, a client's bug can ruin it. Furthermore, if you use an advanced tool
which starts multiple threads to access CVS, you are virtually guaranteed to
have problems at some moment, even if no bugs are triggered - local mode
doesn't allow simultaneous access at all.
>> A safer way is to use a client/server "pserver" mode, even if there is
>> only one CVS user and one machine for client and server.
>
> CVS over SSH should be preferred to pserver.
For a single-machine setup?!
- WBR, Alexey Proskuryakov
Miro Jurisic - 04 Mar 2004 13:38 GMT
> On 03.03.2004 18:46, in article
> macdev-861666.10463403032004@senator-bedfellow.mit.edu, "Miro Jurisic"
[quoted text clipped - 6 lines]
>
> For a single-machine setup?!
On OSes that come with an SSH server (which is pretty much everything except for
Windows), it is easier to set up and more secure than pserver.
meeroh

Signature
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>
Miro Jurisic - 04 Mar 2004 13:50 GMT
> Well, you can always search Google for "CVS local mode repository corrupt"
> to get a ton of hits :). I think that I read this in one of the CVSNT
> installation HOWTOs, which says "local: Should never be used by CVS clients
> as accessing raw repository files will result in corrupt files and dangling
> file locks": http://www.ypsolog.com/docs/comp/windows/cvsnt.html
I did. All I found was a lot of articles about corrupting your repository files
by using incorrect -k flags, and one article (the one you refer to) that is
windows specific and makes a passing and unsubstantiated mention of possible
corruption. I am sorry, but reading the rest of that article did not impress me
with its technical accuracy, and it states upfront that it specifically refers
to an enhanced Windows version of CVS. I have no reason to believe this bug
exists in other versions of CVS.
> Actually, this is quite obvious. If you expose your full repository to the
> client, a client's bug can ruin it.
Actually, when you run the server, the same cvs binary runs on the server
anyway, so a bug in the client or the server can still eat your repository. I
have not seen this happen in over 8 years of using CVS.
> Furthermore, if you use an advanced tool
> which starts multiple threads to access CVS, you are virtually guaranteed to
> have problems at some moment, even if no bugs are triggered - local mode
> doesn't allow simultaneous access at all.
The local mode uses filesystem locking in precisely the same way the remote mode
does. If you are using a Windows port in which that locking is broken, that is
not a fault of CVS, but of the incompetent people who ported it.
meeroh

Signature
If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>