Why p4 unlock -f Does Not Unlock Open +l File Types

Info & Tags

Article #:
1124
Created:
10/12/09
Modified:
02/17/10
Tags:
exclusive, lock, revert, unlock

Related Articles

  1. RCS & Perforce Command Comparison
  2. Killing Perforce Server Child Processes

PROBLEM

I have a user who is not available who has left some files opened against their workspace that have the exclusive lock file type modifier (+l). I do not want to delete the client to revert the files, but I do want to unlock the files so other users can edit them, but p4 unlock -f does not work.


SOLUTION

The p4 unlock -f command only works with files locked for exclusive editing using the p4 lock command. It fails against files with the +l exclusive lock file type, since unlocking such a file would effectively change the file type, which is likely not what was intended.

To revert these files without deleting the users workspace, follow the p4 revert -k instructions in KB Article #38.