PROBE::NFS.PROC.(3stap)

πŸ’… NAME

probe::nfs.proc.rename β€” bestie, your NFS client is out here renaming a file on the server and we are WATCHING it happen ✨


πŸ¦‹ SYNOPSIS

probe nfs.proc.rename {}

That's it. No args. No drama. She just is.


🌸 VALUES

Okay so when this probe fires, she hands you a whole little gift bag of context. Every single thing you get, no skips:

  • old_fh β€” the file handle of the old parent dir. like, the folder the file is moving OUT of πŸšͺ
  • new_name β€” the brand new file name. glow-up name. the rebrand πŸ’–
  • new_filelen β€” length of new_name, in case you needed to count the letters (we support you)
  • server_ip β€” the IP address of the server. the actual address of the whole situation 🌐
  • new_fh β€” file handle of the new parent dir. the folder it's moving INTO. new home, new vibes 🏠
  • prot β€” the transfer protocol. how the tea is being transported β˜•
  • old_name β€” the old file name. the before. the pre-glow-up era 😭
  • old_filelen β€” length of old_name. yes she also counts. equal treatment πŸ’…
  • version β€” the NFS version. and bestie, read this carefully: the function is used for all NFS version. every single one. she does not discriminate πŸ‘‘

πŸŽ€ SEE ALSO


okay that's the page!! this was the SystemTap Tapset Reference, living in section 3stap, dated September 2026 β€” thank you for coming to my TED talk, mwah πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from