The advantage of this lock factory over /// {@link SimpleFSLockFactory} is that the locks should be /// "correct", whereas {@link SimpleFSLockFactory} uses /// java.io.File.createNewFile which /// has warnings about not /// using it for locking. Furthermore, if the JVM crashes, /// the OS will free any held locks, whereas /// {@link SimpleFSLockFactory} will keep the locks held, requiring /// manual removal before re-running Lucene.
/// ///Note that, unlike {@link SimpleFSLockFactory}, the existence of /// leftover lock files in the filesystem on exiting the JVM /// is fine because the OS will free the locks held against /// these files even though the files still remain.
/// ///Native locks file names have the substring "-n-", which /// you can use to differentiate them from lock files created /// by {@link SimpleFSLockFactory}.
/// ///Lucene.Net.lockDir
/// system property. If that is not set, then java.io.tmpdir
/// system property is used.
///