1
0

remove 1.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. .TH REMOVE 5
  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 (like
  39. .IR fs (4))
  40. remove the file immediately: attempts to use the other fids
  41. will yield a
  42. ``phase error.''
  43. .IR U9fs (4)
  44. follows the semantics of the underlying Unix file system,
  45. so other fids typically remain usable.
  46. .SH ENTRY POINTS
  47. .B Remove
  48. messages are generated by
  49. .IR remove .