Locks a fileset entry in the FLDB
Synopsis
fts lock -fileset {name | ID} [-cell cellname] [{-noauth | -localauth}] [-verbose] [-help]
Options
-fileset {name | ID}
Specifies the complete name or fileset ID number of the fileset whose entry in the Fileset Location Database (FLDB) is to be locked. All
versions of the fileset referenced in the entry are affected by the lock, regardless of whether the read-write, read-only, or backup version of the fileset is specified.
-cell cellname
Specifies the cell where the command is to be run. The default is the local cell of the issuer of the command.
-noauth
Directs fts to use the unprivileged identity nobody as the identity of the issuer of the command. If you use this option, do not use the
-localauth option.
-localauth
Directs fts to use the DFS server principal name of the machine on which the command is issued as the identity of the issuer. Use this option only if the
command is issued from a DFS server machine (a machine that has a DFS server principal in the local Registry Database). You must be logged into the server machine as root for this option to
work. If you use this option, do not use the -noauth option.
-verbose
Directs fts to provide detailed information about its actions as it executes the command.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The fts lock command locks the entry in the FLDB for the fileset indicated with the -fileset option. Locking a fileset's FLDB entry blocks
operations on all versions of the fileset, regardless of whether the read-write, read-only, or backup version of the fileset is indicated with the -fileset option. Locking a fileset's entry
prevents all versions of the fileset from being modified with fts commands.
Privilege Required
The issuer must be listed in the admin.fl files on all Fileset Database machines or own the server entry for each machine on which a version of the
fileset to be locked resides.
Cautions
Do not use this command in normal circumstances. It is useful only if the system administrator wants to guarantee that no one else manipulates the fileset until the
lock is released and if there is reason to believe that locking will not happen automatically. Locking a fileset entry inhibits only operations such as deleting and cloning of the fileset; it does
not prevent the reading of data from the fileset.
Examples
The following command locks the FLDB entry for user.terry:
$ fts lock user.terry
Related Information
Commands: fts unlock(8dfs)