From f7afd949c9e2cc4c5f199e3db6398d1be7fcfea9 Mon Sep 17 00:00:00 2001
From: Joe Rayhawk <jrayhawk@omgwallhack.org>
Date: Sun, 10 Jan 2010 23:29:59 -0800
Subject: Notes: lockfiles: Clarifying criticisms of pure shell approach

---
 notes/lockfiles.mdwn | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'notes')

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,
-- 
cgit v1.2.3