Hi Larry,

Thanks for the prompt response.

You were right on that one. I stopped the ypibnd - NIS binding process and
the things seem to be moving forward.

Now I created a sample project dir 'myproj' having sub-dirs 'bin', 'src' &
'inc'.

When I try to *import* this project into the repository it throws the
following error:

cvs import -m "initial import into CVS" myproj mohit start
cvs server: cannot open /root/.cvsignore: Permission denied

No conflicts created by this import



I found out that the project dir 'myproj' was created but the sub-dirs
were not created.

I tried searching for the '.cvsignore' file. It doesn't exist.

What could be the problem.

Also, how can join the mailing-list if any.

Thanks & Regards,

-Mohit Lad



On Fri, 6 Apr 2001, Larry Jones wrote:

> MOHIT A LAD writes:
> > 
> > My setup:
> > =========
> > redhat 6.2 kernel2.2.14-12
> > cvs1.10.7
> 
> I strongly suggest upgrading to the current release (1.11), which you
> can get from www.cvshome.org, but that isn't what's causing your
> problem.
> 
> > 1> export CVSROOT=:pserver:mohit@baharat:/usr/local/cvsdb 
> > 2> cvs login - successful
> > 3> all other cvs commands return the following error:
> > unrecognized auth response from bharat: YPBINDPROC_DOMAIN: Domain not
> > bound
> 
> You have some kind of an NIS (nee Yellow Pages) problem on the server.
> My guess is that you're using NIS for passwords or groups and the server
> machine is unable to contact the NIS server for your domain.
> 
> > This seems absurd as since the cvs login/logout succeeds the other cvs
> > commands should work. 
> 
> Not true:  logout is purely client side, it doesn't contact the server
> at all.  And for login the server just checks the password and exits, it
> doesn't get around to switching to run as the user.
> 
> -Larry Jones
> 
> Is it too much to ask for an occasional token gesture of appreciation?!
> -- Calvin
> 




_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to