summaryrefslogtreecommitdiff
path: root/notes
diff options
context:
space:
mode:
authorJoe Rayhawk <jrayhawk@omgwallhack.org>2010-01-10 23:29:59 -0800
committerJoe Rayhawk <jrayhawk@omgwallhack.org>2010-01-10 23:29:59 -0800
commitf7afd949c9e2cc4c5f199e3db6398d1be7fcfea9 (patch)
tree9386d3a152b280fd1c432643757514fe43b8032f /notes
parentabc86bec4e00e6b341d88e7140ddb23a643742f4 (diff)
downloadjrayhawk-f7afd949c9e2cc4c5f199e3db6398d1be7fcfea9.tar.gz
jrayhawk-f7afd949c9e2cc4c5f199e3db6398d1be7fcfea9.zip
Notes: lockfiles: Clarifying criticisms of pure shell approach
Diffstat (limited to 'notes')
-rw-r--r--notes/lockfiles.mdwn5
1 files changed, 3 insertions, 2 deletions
diff --git a/notes/lockfiles.mdwn b/notes/lockfiles.mdwn
index 7db4ad8..39eecda 100644
--- a/notes/lockfiles.mdwn
+++ b/notes/lockfiles.mdwn
@@ -3,8 +3,9 @@
## Random example shell scripts out on the web
All locks need a read/compare/delete/write transaction that is not practical
-with the shell alone. Imagine a `sleep` statement in front of the
-`rm stalelock` operation and what that would do to other processes.
+with the shell alone. Imagine a `sleep` statement in front of or inbetween the
+`mv lock stalelock` `unlink stalelock` `write lock` operations and what that
+would do to other processes.
Process name comparison won't work very well as scripts aren't always executed
under their own name or even as their own process. For example,