si locks
displays a user's locks.
Synopsis
si locks [--locker=value] [--fields=field1[:width1],field2[:width2]...] [--height=value] [--width=value] [-x=value] [-y=value] [--hostname=server] [--port=number] [--password=password] [--user=name] [(-?|--usage)] [(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory] [--forceConfirm=[yes|no]] [(-g|--gui)][--quiet][--settingsUI=[gui|default]] [--[no]persist] [--status=[none|gui|default]]
Description
si locks displays all of a user's locks on the target server.
Options
This command takes the universal options available to all
si commands, as well as some general options. See the
options reference page for descriptions.
• --locker=value
specifies the user whose locks are retrieved. If :anyone is specified, all locks in the system are displayed.
• --fields=field1[:width1],field2[:width2]...
The fields available for printing can be one or more of the following:
◦ archive
displays the name of the locked archive.
◦ cpid
displays the change package ID number if it is a lock entry in a change package.
◦ devpath
displays the name of the development path where the lock on the revision was made from. This information is relevant when the locking policy is set to devpath, allowing a single user to have a single lock on an archive per development path.
◦ host
displays the hostname of the computer which the lock was performed on.
◦ member
displays the name of the locked member.
◦ project
displays the name and path of the project where the member revision was locked from. If the member revision was locked from a shared subproject, it is the subproject name and path that are displayed.
◦ revision
displays the locked revision number.
◦ locktype
displays the type of lock on the revision: exclusive or non-exclusive.
◦ sandbox
displays the name of the sandbox where the lock on the revision was made, and is relevant when viewing the information from the machine that locked it.
◦ timestamp
displays the time the archive was locked.
◦ user
displays the user holding the lock.
• --[no]persist
controls whether this presentation of information should continue to be updated as new information becomes available. --nopersist forces a static "snapshot" of information, while --persist gives real-time updates.
Diagnostics
See the
diagnostics reference page for possible exit status values.
Preferences
Using
si setprefs or
si viewprefs, you are able to set or view the preference keys for this command.
See Also
• Commands:
si archiveinfo,
si memberinfo,
si mods,
si print,
si revisioninfo,
si rlog,
si sandboxinfo,
si viewhistory,
si viewlabels,
si viewprojecthistory,
si viewsandbox
• Miscellaneous: