Regular repository corruption -- help needed.

[Arne Babenhauserheide]

Dear Alexander,

Am Donnerstag, 20. Dezember 2012, 00:50:39 schrieb Alexander Krauss:
> - The central repository sits on an NFS mount, which is accessed from
>    a number of machines. (I know that this is not nice, but it is not
>    so easy to change at the moment.)

Would it be possible to just give each developer his own clone to push to?

>       hg push ssh://somemachine//nfs/central/repos

→ hg push ssh://somemachine//nfs/central/repos-USER

Then the server could just run timed pulls to the main repo - if those
don’t add new heads.

That would not fix the whole issue, but it would at least change it
from a world-stopping event to a single-dev-stopping event and thus
would directly reduce the pain for you.

Or even just change it to one pulling and one pushing repo and let the server 
do the synchronization locally (without NFS in between).

→ hg push ssh://somemachine//nfs/central/repos-USER

Then people could not push anymore for some time, but they could still pull. 
And the clone would be purely local:

on the server: 

    rm -r central/repos-push; hg clone central/repos central/repos-push

Best wishes,
Arne
-- 
1w6 sie zu achten,
sie alle zu finden,
in Spiele zu leiten
und sacht zu verbinden.
→ http://1w6.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121221/379991bc/attachment.asc>