[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Understanding problems with NFS & CVS.
From: |
Matt Riechers |
Subject: |
Re: Understanding problems with NFS & CVS. |
Date: |
Wed, 05 Sep 2001 09:11:38 -0400 |
Alex Holst wrote:
>
> I fear I may have misunderstood the problems with NFS and CVS. As the two
> different threads in the archives on NFS didn't clarify the issue for me, I
> hope someone can clarify.
>
> I was under the impression that it was bad to share the CVS repository over
> NFS, so hence I have kept our repository on local disks in a machine that is
> accessed via SSH.
>
> For various reasons, I was queried why the repository is not placed on a NFS
> storage device, mounted on the CVS server which is then accessed via SSH. I
> quoted the NFS sharing problems, but the person retorted saying he has
> experienced large projects using NFS mounted on a frontend machine. Can
> anyone comment on the reliability of this? I don't understand why the
> problems would be any different simply by using a frontend machine. It's
> still NFS with whatever problems it carries with it.
>
> Thanks,
> Alex
Here's an example of an old setup we used without problems:
The repository is hosted on a Solaris NFS mounted drive.
- Solaris clients may mount the repository for editing/cvs.
- NT clients can not map the repository locally. They must use rsh/ssh/pserver.
- NT clients can map the Solaris *sandbox* for editing, but not for cvs.
HTH
-Matt