parrot_locate(1)

💖 parrot_locate(1) — the glow-up edition 💖

okay bestie, sit down, because this one is so fun. it's parrot_locate, and it lives in the Cooperative Computing Tools family (the coolest clique in Unix, no cap). this is your little detective page for finding out where your data actually is. 🔍✨

---

✨ NAME ✨

parrot_locate — tells you the true location of the data stored in a named file. like, where it really lives, not just where it pretends to live. it's giving "expose the truth" energy. 💅

---

🦋 SYNOPSIS 🦋

parrot_locate path

that's it. one argument. she's low maintenance, she's iconic. 👑

---

🌸 DESCRIPTION 🌸

so here's the tea, bestie: parrot_locate uses parrot system calls to figure out where the data stored as the file at <path> is actually located. not the fake location, the real one. main character detective behavior. 🕵️♀️

for example:

• run parrot_locate on a file stored in a chirp multi-volume and it hands you back the server name and the file path on that server where the data is chilling. 🗂️
• run it on a file stored in hdfs and it gives you the list of chunk servers storing the file. yes, a whole list. she's thorough. 📋

⚠️ important, bestie: parrot_locate varies depending on the underlying system. most systems return output in the form "<server>:<real path>", but ngl, that output is not guaranteed. so don't come for her if your system does its own thing. it's giving "results may vary" and honestly? valid. 🙈

---

🎀 OPTIONS 🎀

• none — parrot_locate has no options. zero. zilch. she needs nothing from you except a path. periodt. 💀

---

🌈 ENVIRONMENT VARIABLES 🌈

the environment variables that parrot_locate needs are system dependent. most systems don't use or require any — she's self-sufficient like that. for more info, go read the specific system's documentation, iykyk. 📖

---

⭐ EXIT STATUS ⭐

• on success, it returns zero. slay. ✨
• on failure, it returns non-zero. we don't talk about that. 😭

---

💅 EXAMPLES 💅

okay so, to check the location of a file stored in chirp:

% parrot_run parrot_locate /chirp/server.nd.edu/joe/data
     server.nd.edu:/chirp/server.nd.edu/joe/data

and look at that — the truth, revealed. 💖

or, a file stored in a chirp multi-volume:

% parrot_run parrot_locate /multi/server.nd.edu@multivol/data
     datastore01.nd.edu:multivol/data/ttmtteotsznxewoj

see how it swapped in the actual datastore and the actual file path? that's the whole point. she ate. 🔥

---

👑 COPYRIGHT 👑

The Cooperative Computing Tools are Copyright (C) 2005-2019 The University of Notre Dame. This software is distributed under the GNU General Public License. See the file COPYING for details. 📜

---

🫶 SEE ALSO 🫶

• Cooperative Computing Tools Documentation
• Parrot User Manual
• parrot_run(1) parrot_cp(1) parrot_getacl(1) parrot_setacl(1) parrot_mkalloc(1) parrot_lsalloc(1) parrot_locate(1) parrot_timeout(1) parrot_whoami(1) parrot_mount(1) parrot_md5(1) parrot_package_create(1) parrot_package_run(1) chroot_package_run(1)

---

and that's the whole page, bestie!! 🎀 you're officially fluent in parrot_locate. go find your data, she's waiting. 💜

mwah 💋 — brought to you by CCTools 8.0.0 DEVELOPMENT, version of record, no date drama, just vibes. 🦋