projects
/
git-annex.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
6dfdc37
)
fix typo
author
edward
<edward@web>
Sat, 14 Nov 2015 09:57:40 +0000
(09:57 +0000)
committer
admin
<admin@branchable.com>
Sat, 14 Nov 2015 09:57:40 +0000
(09:57 +0000)
doc/devblog/day_336__pid_locks.mdwn
patch
|
blob
|
history
diff --git
a/doc/devblog/day_336__pid_locks.mdwn
b/doc/devblog/day_336__pid_locks.mdwn
index c59e6444289b180e9636683c2e342d6aac581378..03ca076e65ef2f8e9dda56b5ecb42dbf3abc5ac7 100644
(file)
--- a/
doc/devblog/day_336__pid_locks.mdwn
+++ b/
doc/devblog/day_336__pid_locks.mdwn
@@
-13,7
+13,7
@@
because then the pid in question can be running on a different computer.
Even if you do figure out that a pid lock is stale, how do you then
take over a stale pid lock, without racing with anther process that
also wants to take it over? This was the truely tricky question of the
-day.
.
+day.
I have a possibly slightly novel approach to solve that:
Put a more modern lock file someplace else (eg, /dev/shm)