[svk-users] Two instances of SVK conflicting?

Ethan Mallove ethan.mallove at sun.com
Fri Nov 23 21:35:16 EST 2007


On Wed, Nov/21/2007 10:23:36PM, Micah Elliott wrote:
> On 2007-11-21 Ethan Mallove wrote:
> 
> > Does SVK support two instances of the svk command checking
> > out from the same repository at the same time? E.g., 
> 
> That should work fine.  Parallel checkouts should not be a
> problem... as long as they are not to the same destination.
> 
> > in one shell:
> > 
> >   $ svk co /foo/bar
> > 
> > in another shell:
> > 
> >   $ svk co /foo/bar
> 
> This is pathological.  
>

I'm in different directories in the above case. E.g., to
clarify, it is like this:

  in one shell:

    $ pwd
    /tmp/dir1
    $ svk co /foo/bar

  in another shell:

    $ pwd
    /tmp/dir2
    $ svk co /foo/bar

SVK will say "/foo/bar already locked". So I do this
(which I would think is wrong):

  in one shell:

    $ pwd
    /tmp/dir1
    $ svk co /foo/bar

  in another shell:

    $ pwd
    /tmp/dir2
    $ svk cleanup --all && svk co /foo/bar

FWIW, Mercurial *waits* for the lock to free up, and then
continues the operation instead of exiting. Does maybe a
later SVK version do this?

>
> I wouldn't consider it an svk limitation.  The problem is
> that you've got two processes trying to write to the same
> paths at the same time.  If you serialized those two
> checkouts you'd see svk report something to the effect of
> "no work to do" on the second checkout.  But since in your
> case both are midstream, there is a race condition to
> check existence of and write the same files.
>
> Why would this situation ever arise in practical usage?

  $ svk checkout /foo/bar architecture-1
  $ svk checkout /foo/bar architecture-2
  $ svk checkout /foo/bar architecture-3
  $ ...

-Ethan


> 
> -- 
>                           _ _     ___
>                           |V|icah |- lliott
>                           " "     """
> mde at MicahElliott.com            <><             http://MicahElliott.com
> PGP: 0x7C07CBF0          ICQ: 369060435      Linux/Ubuntu: 417195/12440
> HackerKey: v4sw6YUPCJhw5ln5pr7OPck2ma9u8Lw3m5l6Ui2e7t3b8LDMOen6a3XsMRr5
> _______________________________________________
> svk-users mailing list
> svk-users at lists.bestpractical.com
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/svk-users



More information about the svk-users mailing list