lfc-rm man page
LFC-RM(1) LFC User Commands LFC-RM(1)
lfc-rm - remove LFC files or directories in the name server
[1mlfc-rm [22m[[1m-a[22m] [[1m-f[22m] [[1m-i[22m] [4mfilename[24m...
[1mlfc-rm [22m[[1m-f[22m] [[1m-i[22m] [1m-r [4m[22mdirname[24m...
[1mlfc-rm [22mremoves LFC files or directories in the name server. For direc-
tories either [1m-r [22mor [1m-R [22mmust be present. For regular files, it calls
[1mlfc_unlink [22mwhile for directories, it calls [1mlfc_rmdir[22m.
This requires write permission in the parent directory and the file
itself. If write permission on an entry is denied, the standard input
is a terminal and the [1m-f [22moption is not given, the prompt "override
write protection" appears and if the response is not [1my[22m, the entry is
not deleted. Entries directly under a protected directory are never
[4mpath[24m specifies the LFC pathname. If [4mpath[24m does not start with [1m/[22m, it
is prefixed by the content of the [1mLFC_HOME [22menvironment variable.
The following options are supported:
[1m-a [22mRemove the [1mmetadata [22minformation about a file [1mand [22mthe [1mmetadata[0m
information about the replicas that it may have. [1mRemember [22mthat
this is a metadata-only operation, it does not remove the repli-
cas physically from the disk. Removing metadata entries about
replicas without removing the replicas from the disks leads to
non-reachable files on disk. Applies only to files, not direc-
[1m-f [22mDo not give an error message if the file/directory does not
[1m-i [22mRequest acknowledge before removing each individual entry.
[1m-R [22mRecursive mode (equivalent to [1m-r[22m).
[1m-r [22mRecursive mode.
This program returns 0 if the operation was successful or >0 if the
[1mCastor_limits(4)[22m, [1mlfc_rmdir(3)[22m, [1mlfc_unlink(3)[0m
[1mLCG Grid Deployment [22mTeam
LFC $Date: 2011/11/04 11:57:00 $ LFC-RM(1)