Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hey Bo, Foriegn mounted drives are possible with ViewCVS and work quite well. We have a build server running IIS and ViewCVS and our CVS repository is stored on a SAN which is only accessable from the CVS Server (which doesn't run IIS and so cannot run ViewCVS). What we did was define a local user on the build server running ViewCVS and the same exact user was defined on the server mounted to the CVS Repository. The user names and passwords on the two must match exactly. Then we defined a share on the server with CVS repository which gives read access the the repository files to the defined local user. ViewCVS then runs as the defined user which means it has rights to the share through a UNC path (windows sees the two users as being the same and gives access). Works perfectly. We then defined ViewCVS to pickup all repositories in the shared drive. Obviously no one else has access to the repository through the share and must use CVS to access the repositories. Trevor "Bo Berglund" <bo.berglund at telia.com> wrote in message news:vgs3b19gdhlntqku6ttoaijqgnm1lkce60 at 4ax.com... > On Thu, 16 Jun 2005 11:45:38 -0700, Manfred Moser > <manfred at cardiocomm.com> wrote: > >>Oh.... that sounds much better. I just tried jcvs and seems not to support >>the >>sserver protocol. Maybe I got more luck with viewcvs. > > ViewCvs does not use any protocol at all! It parses the RCS files all > by itself, but can be configured to use the cvsnt executable for the > parsing. But that use is *not* via the client/server protocol at all, > it still accesses the RCS files directly. > And this is the reason ViewCvs cannot be used on anything else than a > repository stored on a local hard drive, no foreign mounted drives are > possible. > > > /Bo > (Bo Berglund, developer in Sweden)