Skip to content
Browse files

corrected typos in README

  • Loading branch information...
1 parent c679247 commit ef8b9a76736c59793547e8b33570b5bb262d3d99 @harisankarh committed Aug 18, 2012
Showing with 4 additions and 4 deletions.
  1. +4 −4 README
View
8 README
@@ -1,7 +1,7 @@
Mutef: Mutually exclusive file access for applications
------------------------------------------------------
-Some of the applications which read and perform modifications a file do not support warnings when the file is parallely modified form multiple terminals.
+Some of the applications which read and perform modifications on a file do not support warnings when the file is parallely modified from multiple terminals.
I faced this problem when using hnb and decided to write a wrapper script over hnb which provides mutually exclusive file access.
The file mutef.c compiles to a binary which can be used instead of hnb to open the files.
@@ -12,12 +12,12 @@ Steps:
2. cc mutexopenc -o hnb
3. mv ./hnb /usr/bin/hnb
-The first step renames the original hnb binary in the /usr/bin directory. The compiled binary from the mutef.c is becomes the new /usr/bin/hnb.
-Any file can now be opened using the usual "hnb <filename>" command.
+The first step renames the original hnb binary in the /usr/bin directory. The compiled binary from the mutef.c becomes the new /usr/bin/hnb in step 3.
+Any file can now be opened using the usual "hnb <filename>" command, but now with mutually exclusive file access.
The program works as follows:
-First it check whether a lock file(filename + "_lock") exists for the file which is to be opened. If so, it exits after issuing an "already open" warning.
+First it checks whether a lock file(filename + "_lock") exists for the file which is to be opened. If so, it exits after issuing an "already open" warning.
Otherwise, it opens the file after creating a lock file. The lock file is then deleted after the application is closed.
The program can be modified for arbitrary applications with minor modifications.

0 comments on commit ef8b9a7

Please sign in to comment.
Something went wrong with that request. Please try again.