[cvsnt] Question about multi users working on same machine.

[Bo Berglund]

One caveat when using integrated :sspi: authentication is that if the
users are using any kind of locks on the files like reserved edits etc
then the lock is held by the original user who logged on to that PC
and he is the only one who can release the lock. CVS stores the user
with the lock on the server.
So this makes any other user trying to commit from this sandbox fail.

Locks are generally bad except possibly for binary files.

/Bo


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of keith d. zimmerman
Sent: den 8 november 2004 13:56
To: Peter Crowther
Cc: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Question about multi users working on same machine.


Peter Crowther wrote:
>>From: pierce li [mailto:pierce.li at utstar.com] 
>>I guess the hidden 'CVS' folder can't hold two different 
>>users infomation at the same time, can it? How can I solve 
>>this problem? I'm really suffered. Thanks!
> 
> 
> Ensure that each user checks out from CVS into their own sandbox.
> Sandboxes are one-per-user, not one-per-machine.
> 
> 		- Peter
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> 

This is not entirely true when working with integrated logins (SSPI). 
If you use the :sspi: protocol, and do not specify a user name, cvsnt 
will use your windows account.... Then, when another user comes along to 
use the same sandbox, windows will use *his* (or her) windows username. 
  Provided that their permissions are the same on the repository all 
should be well.

Now, it may bear asking why you are using CVS at all if you are all 
using one common set of files.....

-kz
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt