📄 rm.1
字号:
.\" Copyright (c) 1990, 1993, 1994.\" The Regents of the University of California. All rights reserved..\".\" This code is derived from software contributed to Berkeley by.\" the Institute of Electrical and Electronics Engineers, Inc..\".\" Redistribution and use in source and binary forms, with or without.\" modification, are permitted provided that the following conditions.\" are met:.\" 1. Redistributions of source code must retain the above copyright.\" notice, this list of conditions and the following disclaimer..\" 2. Redistributions in binary form must reproduce the above copyright.\" notice, this list of conditions and the following disclaimer in the.\" documentation and/or other materials provided with the distribution..\" 3. All advertising materials mentioning features or use of this software.\" must display the following acknowledgement:.\" This product includes software developed by the University of.\" California, Berkeley and its contributors..\" 4. Neither the name of the University nor the names of its contributors.\" may be used to endorse or promote products derived from this software.\" without specific prior written permission..\".\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION).\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF.\" SUCH DAMAGE..\".\" @(#)rm.1 8.2 (Berkeley) 4/18/94.\".Dd April 18, 1994.Dt RM 1.Os.Sh NAME.Nm rm.Nd remove directory entries.Sh SYNOPSIS.Nm rm.Op Fl f | Fl i.Op Fl dPRr.Ar file ....Sh DESCRIPTIONThe.Nm rmutility attempts to remove the non-directory type files specified on thecommand line.If the permissions of the file do not permit writing, and the standardinput device is a terminal, the user is prompted (on the standard erroroutput) for confirmation..PpThe options are as follows:.Bl -tag -width flag.It Fl dAttempt to remove directories as well as other types of files..It Fl fAttempt to remove the files without prompting for confirmation,regardless of the file's permissions.If the file does not exist, do not display a diagnostic message or modifythe exit status to reflect an error.The.Fl foption overrides any previous.Fl i options..It Fl iRequest confirmation before attempting to remove each file, regardless ofthe file's permissions, or whether or not the standard input device is aterminal.The.Fl ioption overrides any previous.Fl f options..It Fl POverwrite 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..It Fl RAttempt to remove the file hierarchy rooted in each file argument.The .Fl Roption implies the.Fl doption.If the.Fl ioption is specified, the user is prompted for confirmation before each directory's contents are processed (as well as before the attemptis made to remove the directory).If the user does not respond affirmatively, the file hierarchy rooted inthat directory is skipped..Pp.It Fl rEquivalent to.Fl R ..El.PpThe.Nm rmutility removes symbolic links, not the files referenced by the links..PpIt is an error to attempt to remove the files ``.'' and ``..''..PpThe.Nm rmutility exits 0 if all of the named files or file hierarchies were removed,or if the.Fl foption was specified and all of the existing files or file hierarchies wereremoved.If an error occurs,.Nm rmexits with a value >0..Sh SEE ALSO.Xr rmdir 1 ,.Xr unlink 2 ,.Xr fts 3 ,.Xr symlink 7.Sh BUGSThe.Fl Poption assumes that the underlying file system is a fixed-block filesystem.UFS is a fixed-block file system, LFS is not.In addition, only regular files are overwritten, other types of filesare not..Sh COMPATIBILITYThe.Nm rmutility differs from historical implementations in that the.Fl foption only masks attempts to remove non-existent files instead ofmasking a large variety of errors..PpAlso, historical.Bximplementations prompted on the standard output,not the standard error output..Sh STANDARDSThe.Nm rmcommand is expected to be.St -p1003.2compatible.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -