So we did a log of this on IRC with -Dtransport. This shows the held->tmp rename succeeding, a nd the subsequent
rm tmp/info
rmd tmp
succeeding too, but the lock remains in place.
my theory is a virus scanner or some such interfering.
Some things we can do to narrow it down:
-add a read-back after the rename to make sure it does rename away successfully.
Something we did:
-tried a 2s delay before the rename, but this didn't appear to have any effect.
So we did a log of this on IRC with -Dtransport. This shows the held->tmp rename succeeding, a nd the subsequent
rm tmp/info
rmd tmp
succeeding too, but the lock remains in place.
my theory is a virus scanner or some such interfering.
Some things we can do to narrow it down:
-add a read-back after the rename to make sure it does rename away successfully.
Something we did:
-tried a 2s delay before the rename, but this didn't appear to have any effect.