[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: More archive corruption!!

From: Tom Lord
Subject: Re: [Gnu-arch-users] Re: More archive corruption!!
Date: Mon, 12 Apr 2004 11:51:04 -0700 (PDT)

    > From: Stefan Monnier <address@hidden>

    >> If there is a held one in the parent dir then it happened presumably
    >> because some earlier attempt to commit was interrupted.

    > Doesn't tla catch this interrupt and clean up the lock before
    > exiting?

It could and perhaps should but the problem could still occur if, for
example, a network connection to an archive were lost.   That change
would catch some but not all cases.

That's why `lock-revision --break' exists, along with the carefully
designed locking protocol:  so that although archive's can wind up in
a momentarily inconvenient state, they can't actually become wedged.

The weird thing is, it's very, very, very common for newbies
(presumably mostly coming from CVS) to assume that the condition
solved by `lock-revision --break' is actually a wedged archive and to
figure out for themselves how to fix it "by hand" on the server.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]