I forgot to mention that I just upgraded darcs on that machine from
1.0.9 to 2.4.0. With 1.0.9 I've never seen this and it was running for
months synchronizing those repositories via cron.
What changed in all this was the darcs version on the machine doing
the pull (from 1.0.9 to 2.4.0) and the source repositories that were
upgraded from the darcs-1 format to the hashed format.
I will upgrade the destination repositories to the hashed format as
well and I'll report back if that changed anything.
On 22 Apr 2010, at 15:43, Dan Pascu wrote:
In the same context I mentioned before (a cron job running darcs
pull -aq for about 8 repositories every 30 minutes) I see this
message sometimes:
Waiting for lock /home/repositories/callcontrol/_darcs/lock
Couldn't get lock /home/repositories/callcontrol/_darcs/lock
The repository name may vary, but it's a subset of the 8
repositories (I've seen 2-3 of them regularly while the others I
never seen giving this error).
Any idea what could be causing this?
I should mention that none is doing any write operations in those
repositories except the cron job that does pull regularly. Otherwise
the repositories are used by trac-darcs in a read-only mode (show
patches, files, ...). Is it possible that a read-only operation that
trac-darcs uses to inspect the repo may lock it so a pull is not
possible at that moment?
--
Dan
_______________________________________________
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
--
Dan
_______________________________________________
darcs-users mailing list
darcs-users@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-users
