1 .TH REMOVE 9P 
2 .SH NAME
3 remove \- remove a file from a server
4 .SH SYNOPSIS
5 .ta \w'\fLTremove 'u
6 .IR size [4]
7 .B Tremove
8 .IR tag [2]
9 .IR fid [4]
10 .br
11 .IR size [4]
12 .B Rremove
13 .IR tag [2]
14 .SH DESCRIPTION
15 The
16 .B remove
17 request asks the file server both to remove the file represented by
18 .I fid
19 and to
20 .B clunk
21 the
22 .IR fid ,
23 even if the remove fails.
24 This request will fail if the client does not have write permission
25 in the parent directory.
26 .PP
27 It is correct to consider
28 .B remove
29 to be a
30 .B clunk
31 with the side effect of removing the file if permissions allow.
32 .PP
33 If a file has been opened as multiple fids,
34 possibly on different connections,
35 and one fid is used to remove the file,
36 whether the other fids continue to provide access to the file
37 is implementation-defined.
38 The Plan 9 file servers
39 remove the file immediately: attempts to use the other fids
40 will yield a
41 ``phase error.''
42 .IR U9fs
43 follows the semantics of the underlying Unix file system,
44 so other fids typically remain usable.
45 .SH ENTRY POINTS
46 .I Fsremove
47 (see
48 .MR 9pclient (3) )
49 generates
50 .B remove
51 messages.