break-lock should check whether the lock-holding process is still alive
Bug #397298 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
When about to break a lock, if it's apparently currently held by a process on the local machine, bzr could check if that process still exists, and if so refuse to break it.
This is not foolproof because pids can be reused and it may be hard to tell if the lock really came from the same machine, but we could often get it right.
There have been several user bug reports of trying to run break-lock when the process is still running.
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| tags: | added: check-for-breezy |
To post a comment you must log in.
In the fix for bug 220464 this is basically done, but for refusing to automatically break the lock rather than not giving the option at all.