3 vos_lock - Locks a VLDB volume entry
10 B<vos lock> S<<< B<-id> <I<volume name or ID>> >>>
11 S<<< [B<-cell> <I<cell name>>] >>>
12 [B<-noauth>] [B<-localauth>]
13 [B<-verbose>] [B<-encrypt>] [B<-noresolve>]
14 S<<< [B<-config> <I<config directory>>] >>>
17 B<vos lo> S<<< B<-i> <I<volume name or ID>> >>>
18 S<<< [B<-c> <I<cell name>>] >>>
19 [B<-noa>] [B<-l>] [B<-v>] [B<-e>] [B<-nor>]
20 S<<< [B<-co> <I<config directory>>] >>>
28 The B<vos lock> command locks the Volume Location Database (VLDB) entry
29 for the indicated volume, blocking any operation that requires a write to
30 that entry. The lock applies to all of the volume versions associated with
31 the entry, not just the one specified with the B<-id> argument.
33 To unlock a single VLDB entry, use the B<vos unlock> command. To unlock
34 several entries, or all locked entries in the VLDB, use the B<vos
39 Do not use this command in normal circumstances. It is useful for
40 guaranteeing that the volume stays unchanged when there is reason to
41 believe that volume operations cannot properly lock VLDB volume entries as
42 they normally do to synchronize with one another.
48 =item B<-id> <I<volume name or ID>>
50 Specifies either the complete name or volume ID number of a volume of the
51 any of the three types.
53 =include fragments/vos-common.pod
59 The following command locks the VLDB entry for C<user.terry>.
63 =head1 PRIVILEGE REQUIRED
65 The issuer must be listed in the F</usr/afs/etc/UserList> file on the
66 machine specified with the B<-server> argument and on each database server
67 machine. If the B<-localauth> flag is included, the issuer must instead be
68 logged on to a server machine as the local superuser C<root>.
78 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
80 This documentation is covered by the IBM Public License Version 1.0. It was
81 converted from HTML to POD by software written by Chas Williams and Russ
82 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.