The information in this article applies to:
- Microsoft Visual SourceSafe, versions 4.0, 5.0
- SourceSafe for MS-DOS, versions 2.X, 3.0X
- SourceSafe for Windows, versions 2.X, 3.0X
- SourceSafe for Macintosh, versions 2.X, 3.0X
- SourceSafe for Windows NT, versions 2.X, 3.0X
- SourceSafe for UNIX, versions 2.X, 3.0X
SUMMARY
SourceSafe can use two methods for locking files:
- Native: SourceSafe uses operating-system native locking mechanisms.
This is the fastest method, but it may not operate correctly under all
network configurations.
- Lockmode: SourceSafe creates files in the DATA\LOCKS directory
indicating a database file is locked. This method is slower, but will
work on all configurations. However, users must have delete rights to
the DATA\LOCKS directory.
SourceSafe uses the native setting by default.
MORE INFORMATION
The following problems indicate you need to use the lockmode setting:
- The error "Error locking file."
- SourceSafe seems to hang (stop responding) after performing an operation
such as Checkout, Update, adding a file, or creating a project.
To solve these problems, change the locking method globally for all
SourceSafe users by adding or changing the Lock_Mode setting in the
SRCSAFE.INI (or in version 2.X, the SYSTEM.INI file).
Edit the SRCSAFE.INI file, which is located in the SourceSafe directory to
add:
lock_mode = lockfile
In version 2.X, edit the SYSTEM.INI file in the SourceSafe directory to
add:
lock_mode = pedantic
REFERENCES
Microsoft SourceSafe Concepts and Configuration Manual, Section 5
The SourceSafe Administrator
|