CLUNK(9P)
β¨ NAME β¨
clunk β forget about a fid. yep, that's the whole NAME, and this is the CLUNK(9P) page, bestie π
π¦ SYNOPSIS π¦
size[4] Tclunk tag[2] fid[4]
size[4] Rclunk tag[2]
π DESCRIPTION π
okay so the clunk request is basically you telling the file server: βbestie, the client is done with the current file that fid points to, we can let it go π«Άβ. important plot twist though β the actual file does not get removed on the server, unless that fid had been opened with ORCLOSE. periodt.
once a fid has been clunked, the same fid can be reused in a new walk or attach request. slay, recycling π
even if theclunkreturns an error, thefidis no longer valid. no cap, it's done β invalid even on the error path π
π ENTRY POINTS π
clunk transactions are generated by fsclose and fsunmount (see 9pclient(3)), and indirectly by other actions too β like failed fsopen calls. iykyk π
that's the whole CLUNK(9P) situation β no source/version/date footer info on this page, just the manual name, so consider this your cute little sign-off: bye bestie, go clunk responsibly ππ«Άβ¨
π¦ where this page comes from
- alpine 3.24: plan9port-doc 0_git20260208-r0 Β· LPL-1.02
- arch rolling: plan9port 20261021-2 Β· custom
- nixos 26.05: plan9port 0-unstable-2025-11-10
- nixos 26.05: plan9port-wayland 0-unstable-2025-11-26
- nixpkgs unstable: plan9port 0-unstable-2025-11-10
- nixpkgs unstable: plan9port-wayland 0-unstable-2025-11-26
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms