Index: /branches/eam_branches/20090715/Ohana/src/libdvo/doc/locking.txt
===================================================================
--- /branches/eam_branches/20090715/Ohana/src/libdvo/doc/locking.txt	(revision 25101)
+++ /branches/eam_branches/20090715/Ohana/src/libdvo/doc/locking.txt	(revision 25102)
@@ -5,6 +5,9 @@
 are used vs cases of read/write (hard locks) are needed.
 
-DVO uses a somewhat strong locking policy in
-order to prevent users from getting inconsistent data.  This is good,
-but it prevents DVO letting users have read-only UNIX permissions on a
-database: it is necessary to have wrte from being able tb
+locks set in DVO:
+
+dvo_catalog_lock -- on catalog open & catalog create (all files for
+		    split mode)
+
+gfits_db_lock -- on photcode table read/write and dvo_image_lock
+
