# HG changeset patch # User Karl Heuer # Date 858590732 0 # Node ID f36d8f965ab54fdbe49ed55213b2ad6953a2b200 # Parent 024399a1b442790f85419a7f3277f32add48b152 Fix typos in comment. diff -r 024399a1b442 -r f36d8f965ab5 src/filelock.c --- a/src/filelock.c Sat Mar 15 13:26:59 1997 +0000 +++ b/src/filelock.c Mon Mar 17 09:25:32 1997 +0000 @@ -58,14 +58,14 @@ that's too unreliable. Hence the separate file, which could theoretically be updated by daemons running separately -- but this whole idea is unimplemented; in practice, at least in our - environment, it seems such stale locks arise fiarly infrequently, and + environment, it seems such stale locks arise fairly infrequently, and Emacs' standard methods of dealing with clashes suffice. We use symlinks instead of normal files because (1) they can be stored more efficiently on the filesystem, since the kernel knows they will be small, and (2) all the info about the lock can be read in a single system call (readlink). Although we could use regular - files to be useful on old systems lacking symlinks, noawdays + files to be useful on old systems lacking symlinks, nowadays virtually all such systems are probably single-user anyway, so it didn't seem worth the complication.