Release the lock on a file.
p4 [g-opts] unlock [-c change | -s shelvedchange | -x] [-f] [file ...]
p4 [g-opts] -c client unlock [-f ] -r
p4 [g-opts] -g -c change [-f ]
The p4 unlock
command includes three syntax
variants:
The first syntax variant releases locks that were created explicitly
using the p4 lock
command or implicitly during the course of a submit operation or
other operations that require file locking.
If the file is open in a pending changelist other than
default
, you must use the -c
option to
specify the pending changelist. If no changelist is specified,
p4 unlock
unlocks files in the default
changelist.
If no file name is given, all files in the designated changelist are unlocked.
The second syntax variant allows you to unlock files that were left
locked due to a failed p4
push
command.
If a p4 push
command
from a remote server to this server fails, files can be left locked
on this server, preventing other users from submitting changes that
affect these files. In this case, the user who issued the p4 push
command can use
the -r
option of the p4
push
command (and specify the name of the client
that was used on that remote server) to unlock the files on this
server. An administrator can run p4 unlock -f -r
as well. For example:
$ p4 -p central -c myworkspace unlock -r
-c changelist
option.By default, files can be unlocked only by the changelist owner, who must
also be the user who has the files locked. However, administrators on the commit server can use the -fx
option:
$ p4 -c myclient unlock -xf myfile
Consider that when the administrator uses the -fx option, the administrator undoes a feature of the +1 file type described at File type modifiers. The exclusive lock for editing of the +1 file type is meant to prevent other users from being able to affect the file.
For an alternative approach to managing the files of an absent user, see the Support Knowledgebase article, "Reverting Another User's Files".
|
Unlock files in pending changelist
|
|
Superuser or administrator force option that allows unlocking of files opened by other users. |
|
Unlock the files associated with the specified client that were
locked due to a failed |
|
If a file is locked in a pending shelved changelist, unlock it
and keep it within the |
|
In distributed environments, unlock files that have the
|
|
See Global Options. |
Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
---|---|---|
No |
No |
|
To lock files so other users can’t submit them |
|
To display all your open, locked files (UNIX) |
|