FS_GETCLIENTADDRS(1)

💖 FS_GETCLIENTADDRS ✨

okay bestie, welcome to the OpenAFS corner of the man pages, this is fs_getclientaddrs from the AFS Command Reference and it's literally just "hey, tell me which interfaces I'm putting on blast" 💅

---

🌸 NAME 🌸

fs_getclientaddrs — shows you the client interfaces that are getting registered 🫶

---

✨ SYNOPSIS ✨

fs getclientaddrs [-help]

fs gc [-h]

fs getcl [-h]

three whole ways to say the same thing, we love options (literally, there's options) 💖

---

🦋 DESCRIPTION 🦋

So fs getclientaddrs shows you the IP addresses of the interfaces that your local Cache Manager registers with a File Server the very first time it connects to it. like, first impressions, but make it networking 🌈

The File Server uses those addresses when it initiates a remote procedure call (RPC) to the Cache Manager — yes, the opposite direction of when it's just replying to an RPC the Cache Manager sent. And there are two common moments where the File Server is the one starting the convo:

• when it breaks callbacks 💀
• when it pings the client machine to double check the Cache Manager is still reachable 👀

If an RPC to one of those interfaces fails, the File Server goes "okay directed broadcast energy" and simultaneously sends RPCs to all of the other interfaces in the list, just to figure out which ones are still up. Whichever one replies first? That's the one it's sticking with — that's the interface it'll use for pings and for RPCs to break callbacks. winner winner 🏆

And if you wanna know how the Cache Manager builds that list automatically in kernel memory when it initializes, or how to change the kernel list after initialization? fs_setclientaddrs(1) has you covered, bestie, go read that one ✨

---

😭 CAUTIONS 😭

okay so this is the part where I hold your hand. these are important. pay attention.

• The File Server only uses the list of interfaces shown by this command when it's picking an alternative interface after it failed to break a callback or ping the Cache Manager. When it's replying to the Cache Manager's request for file system data, it replies to the interface the Cache Manager used when sending that request. Full stop. And if the File Server's reply to a data request fails? Then the file server machine's network routing configuration is what decides which alternate network routes back to the client machine are available for resending the reply. Not this list. Not today.
• The displayed list applies to all File Servers the Cache Manager connects to in the future. And ngl, it's not practical to register different sets of addresses with different File Servers, because doing that means using the fs setclientaddrs command to change the list and then rebooting each relevant File Server immediately. 😭
• The displayed list isn't necessarily governing the behavior of a given File Server either! If an administrator has issued the fs setclientaddrs command since the Cache Manager first contacted that File Server, then it only determines which addresses the Cache Manager registers when connecting to File Servers in the future. the way that it's future-facing only. 💀
• And the list of interfaces does not influence the Cache Manager's choice of interface when it's establishing a connection to a File Server. hard no, not its job, mind your business 🙈

---

💅 OPTIONS 💅

• -help — prints the online help for this command. And every other valid option? Ignored. bye 👋

---

👑 OUTPUT 👑

The output shows the IP address of each interface that the Cache Manager is currently registering with File Server processes it contacts — one address per line, clean, iconic, no notes ⭐

The File Server initially uses the first address for breaking callbacks and pinging the Cache Manager. But the ordering of all the other interfaces? Not meaningful. it's giving unbothered, it's giving no rank 🌸

---

🍓 EXAMPLES 🍓

Here's the Cache Manager registering two interfaces with File Servers, look at her go:

% fs getclientaddrs
192.12.105.68
192.12.108.84

slay 💖

---

🧚 PRIVILEGE REQUIRED 🧚

None 🫶 (we love a low-barrier-to-entry queen)

---

🌈 SEE ALSO 🌈

fileserver(8), fs_setclientaddrs(1)

go read your sisters, bestie, iykyk 💜

---

💜 COPYRIGHT 💜

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

---

that's the whole page, no cap, every flag and caution intact 🎀 this was brought to you by OpenAFS, version dated 2026-07-27, and yes the footer said FS_GETCLIENTADDRS(1) twice because man pages are extra like that. periodt. 💅✨