10564b1175
groff 1.23.0 added .MR to its -man macro package. The NEWS file states
that the inclusion of the macro "was prompted by its introduction to
Plan 9 from User Space's troff in August 2020." From d32deab it seems
that the name for Plan 9 from User Space's implementation was suggested
by groff maintainer G. Brandon Robinson.
Not sure if the intention was to make these definitions compatible, but
it would be nice if they were.
Currently, Plan 9 from User Space's .MR expects its second argument to
be parenthesized. groff's .MR does not. This results in extra
parentheses appearing in manual references when viewing Plan 9 from User
Space's manual pages on a system using groff.
52 lines
1.0 KiB
Plaintext
52 lines
1.0 KiB
Plaintext
.TH REMOVE 9P
|
|
.SH NAME
|
|
remove \- remove a file from a server
|
|
.SH SYNOPSIS
|
|
.ta \w'\fLTremove 'u
|
|
.IR size [4]
|
|
.B Tremove
|
|
.IR tag [2]
|
|
.IR fid [4]
|
|
.br
|
|
.IR size [4]
|
|
.B Rremove
|
|
.IR tag [2]
|
|
.SH DESCRIPTION
|
|
The
|
|
.B remove
|
|
request asks the file server both to remove the file represented by
|
|
.I fid
|
|
and to
|
|
.B clunk
|
|
the
|
|
.IR fid ,
|
|
even if the remove fails.
|
|
This request will fail if the client does not have write permission
|
|
in the parent directory.
|
|
.PP
|
|
It is correct to consider
|
|
.B remove
|
|
to be a
|
|
.B clunk
|
|
with the side effect of removing the file if permissions allow.
|
|
.PP
|
|
If a file has been opened as multiple fids,
|
|
possibly on different connections,
|
|
and one fid is used to remove the file,
|
|
whether the other fids continue to provide access to the file
|
|
is implementation-defined.
|
|
The Plan 9 file servers
|
|
remove the file immediately: attempts to use the other fids
|
|
will yield a
|
|
``phase error.''
|
|
.IR U9fs
|
|
follows the semantics of the underlying Unix file system,
|
|
so other fids typically remain usable.
|
|
.SH ENTRY POINTS
|
|
.I Fsremove
|
|
(see
|
|
.MR 9pclient 3 )
|
|
generates
|
|
.B remove
|
|
messages.
|