BK-UNLOCK(1)

💅 bk unlock — remove BitKeeper repository locks 💅

okay so this is the BitKeeper User’s Manual page for bk unlock (page id: bk unlock(none)), and it’s giving “cleanup era” ✨. bestie, this is the command you hope you never need, but when a lock is being a little gremlin, here’s the tea. 🫶

---

🌸 NAME 🌸

• bk unlock — remove BitKeeper repository locks 💖

✨ SYNOPSIS ✨

bk unlock [−rsw] [file ...]

💖 DESCRIPTION 💖

The unlock command can be used to remove locks which have been left behind for some reason. lowkey that’s the whole plot. 😭

In general, you shouldn’t need this command — if you do, it indicates that BitKeeper is leaving lock files that it should not. In that case, please tell support@bitkeeper.com so we can fix that problem. please and thank you, bestie 🫶

The unlock command can be used to remove repository level locks. This can be necessary if a remote process has left behind a lock (local stale locks are detected and cleaned automatically). A stale lock is one which has been created locally but the process is no longer present. okay so stale = local-made but the process ghosted 👻.

Note: a repository can have two write locks: the regular lock file and the existence of the RESYNC directory. Removing the write lock does not imply removing the RESYNC directory, see bk help abort for that. 🚨 no cap, RESYNC is its own whole situation.

💅 OPTIONS 💅

• −r — Remove all read locks, stale or not. all of ’em, periodt.
• −s — Remove both read and write locks, but only if they are stale. stale-only vibe check.
• −w — Remove the write lock, stale or not. Does not remove the RESYNC directory. yes, it said what it said 🫣

🦋 SEE ALSO 🦋

• bk‐lock
• bk‐abort

👑 CATEGORY 👑

• File
• Repository

---

sign-off time, bestie: BitKeeper Inc, version 1E1, page bk unlock(none); date: not listed on this page. that’s the whole manual-page moment — mwah 💋✨