NAME
rrmm, uunnlliinnkk - remove directory entries
SYNOPSIS
rrmm [-ddffiiPPRRrrvvWW] file ...
uunnlliinnkk fileDESCRIPTION
The rrmm utility attempts to remove the non-directory type files specified
on the command line. If the permissions of the file do not permit writ-
ing, and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation. The options are as follows:-dd Attempt to remove directories as well as other types of
files.-ff Attempt to remove the files without prompting for confirma-
tion, regardless of the file's permissions. If the file does not exist, do not display a diagnostic message or modify theexit status to reflect an error. The -ff option overrides any
previous -ii options.
-ii Request confirmation before attempting to remove each file,
regardless of the file's permissions, or whether or not thestandard input device is a terminal. The -ii option overrides
any previous -ff options.
-PP Overwrite regular files before deleting them. Files are
overwritten three times, first with the byte pattern 0xff, then 0x00, and then 0xff again, before they are deleted.-RR Attempt to remove the file hierarchy rooted in each file
argument. The -RR option implies the -dd option. If the -ii
option is specified, the user is prompted for confirmation before each directory's contents are processed (as well as before the attempt is made to remove the directory). If the user does not respond affirmatively, the file hierarchy rooted in that directory is skipped.-rr Equivalent to -RR.
-vv Be verbose when deleting files, showing them as they are
removed.-WW Attempt to undelete the named files. Currently, this option
can only be used to recover files covered by whiteouts. The rrmm utility removes symbolic links, not the files referenced by the links. It is an error to attempt to remove the files ``.'' or ``..''. When the utility is called as uunnlliinnkk, only one argument, which must notbe a directory, may be supplied. No options may be supplied in this sim-
ple mode of operation, which performs an unlink(2) operation on the
passed argument. The rrmm utility exits 0 if all of the named files or file hierarchies wereremoved, or if the -ff option was specified and all of the existing files
or file hierarchies were removed. If an error occurs, rrmm exits with a value >0. NNOOTTEE The rrmm command uses getopt(3) to parse its arguments, which allows it toaccept the `-' option which will cause it to stop processing flag
options at that point. This will allow the removal of file names thatbegin with a dash (`-'). For example:
rm - -filename
The same behavior can be obtained by using an absolute or relative path reference. For example:rm /home/user/-filename
rm ./-filename
SEE ALSO
rmdir(1), undelete(2), unlink(2), fts(3), getopt(3), symlink(7)
BUGS
The -PP option assumes that the underlying file system is a fixed-block
file system. In addition, only regular files are overwritten, other types of files are not. CCOOMMPPAATTIIBBIILLIITTYYThe rrmm utility differs from historical implementations in that the -ff
option only masks attempts to remove non-existent files instead of mask-
ing a large variety of errors. The -vv option is non-standard and its use
in scripts is not recommended. Also, historical BSD implementations prompted on the standard output, not the standard error output. STANDARDS The rrmm command is almost IEEE Std 1003.2 (``POSIX.2'') compatible, except that POSIX requires rrmm to act like rmdir(1) when the file specified is adirectory. This implementation requires the -dd option if such behavior
is desired. This follows the historical behavior of rrmm with respect to directories. The simplified uunnlliinnkk command conforms to Version 2 of the Single UNIX Specification (``SUSv2''). HISTORY A rrmm command appeared in Version 1 AT&T UNIX. BSD January 28, 1999 BSD