Fossil SCM
database is locked error for 'fossil all' commands that need to modify the config database
b6eea9446d61d73…
· opened 12 years, 8 months ago
- Type
- Code_Defect
- Priority
- Medium
- Severity
- Important
- Resolution
- Overcome_By_Events
- Subsystem
- —
- Created
- Sept. 27, 2013 11:11 a.m. UTC
When using a 'fossil all' command, such as 'fossil all pull' that ends up needing to modify a configuration setting (e.g. "always trust this SSL certificate"), it fails with a "database is locked" error, presumably because the parent Fossil process is holding a lock on it.
Comments (5)
When using a 'fossil all' command, such as 'fossil all pull' that ends up needing to modify a configuration setting (e.g. "always trust this SSL certificate"), it fails with a "database is locked" error, presumably because the parent Fossil process is holding a lock on it.
Candidate fix is now on the tkt-b6eea9446d branch.
Direct link to changes is:
[/vdiff?from=ec81aee9156f43f4&to=tkt-b6eea9446d]
Updated branch with the latest trunk changes.
This issue was fixed at some point, without requiring the special changes on the ticket branch.