SmodD
From SRB
Contents |
[edit]
NAME
SmodD - modifies metadata information about SRB data objects.
[edit]
SYNOPSIS
SmodD [-s|-t|-c|-g|-H|-k|-x|-X|-y|-Y|-z] newValue dataName
SmodD [-L|-P] newValue additionalValue dataName
SmodD -l targetDataName targetCollectionName dataName
SmodD -T dataName
SmodD -V replicaNumber oldVersionString newVersionString dataName
[edit]
DESCRIPTION
SmodD modifies information about data objects dataName.
Note that the command can change the information for more than one object if dataName can resolve to more than one object name.
The Stoken utility can be used to find the current data types supported.
[edit]
OPTIONS
- -h
- display command options
- -s
- change size
- -t
- change type
- -l
- makes a soft link for this data in another collection targetCollectionName with a given targetDataName
- -c
- insert comments
- -g
- insert GUID - global unique identifier
- -T
- moves the data to trash
- -V
- changes the version from oldVersionString to newVersionString for the copy of the data given by the replicaNumber
- -k
- insert/change checksum
- -Y
- insert/change encrypted field via SRB Secure Communication
- -z
- insert/change compressed field
- -x
- insert/change expiration-date number 1.
- -X
- insert/change expiration-date number 2. These expiration dates may be used to purge files from SRB. This can be done either by the user or an administrator using Srm command.
- -y
- insert/change encryption information. This option will be deprecated. Use -Y instead.
- -H
- hide or unhide a srbObject and disallows user from reading/writing the srbObject Set newValue=1 for hiding and newValue=0 for unhiding. When metadata access control is on, the srbObject will not be seen by Sls.
- -P
- pin or unpin a srbObject and disallows removal of file by a SRB daemon (current implementation does not use the pin from stopping one to remove/move a file) Set newValue=1 for pinning and newValue=0 for unpinning. This operation needs additionalValue and should be of the form YYYY-MM-DD-HH.MM.SS;
- -L
- lock upto a timestamp; newValue can be 'read', 'all' or 'null'. If all-locked no one can read or write. If read-locked no one can write but they can read. If null-locked all locks are removed. This operation needs additionalValue and should be of the form YYYY-MM-DD-HH.MM.SS;
[edit]
