oar_resources_init(8)

💖 NAME 💖

oar_resources_init — bestie, this one connects to a whole list of hosts, scoops up all their system info, and then creates the matching OAR resources for you. It's giving glow-up for your cluster. ✨

---

🌸 SYNOPSIS 🌸

oar_resource_init  [options] <hostfile>

(yes, the synopsis line really does say oar_resource_init — that's exactly how it's printed on the page, so I'm keeping it character for character, no cap 🫶)

---

🦋 DESCRIPTION 🦋

So here's the tea, bestie. Hosts get read from hostfile, one per line — and that file must be readable by the oar user. If hostfile is -, then it reads from STDIN instead. Iconic, flexible, we love her. 💅

The oar-node service must be started on all hosts — because oar_resources_init connects to hosts over OAR's dedicated SSH service. No oar-node, no vibes. 😭

The command has two moods:

• it can just generate a script, so you get to modify it before you execute it, or
• it can directly run the OAR commands (oarnodesetting and oarproperty) and get it over with.

The OAR resource hierarchy it assumes looks like this:

host > cpu > core

If the -t option is set, it adds the thread level on top, so you get:

host > cpu > core > thread

The mem property is set along with the hierarchy. Periodt.

If the -m option is set, it adds the numa level and the numamem property. ⚠️ But beware, babes: the numa hierarchy level may differ from machine to machine, so don't come for me when it does.

If the -g option is set, it adds the gpu level and the gpudevice property. 🙈 Info for the gpu hierarchy and the gpudevice property is however not populated — you can complete it by manually editing the generated script. DIY queen energy.

Other properties can also be added in the generated script, so go off. ✨

And after the execution of the script, other oarnodesetting calls can still be used to change the resource properties. Nothing is locked in, it's not that serious.

---

👑 OPTIONS 👑

• -t — Creates the thread hierarchy level (HyperThreading/SMT). 🧵
• -n — Creates the numa hierarchy level and numamem properties.
• -g — Creates the gpu hierarchy level and gpudevice properties (but not populated, as established 😌).
• -o [file] — Script filename.
• -x — Executes the script at the end and removes it. One and done.
• -y — Assumes "yes" as the answer to all prompts and runs non-interactively. Full auto, no questions asked.
• -v — Prints the generated script. Show me the receipts. 🔍
• -e [path] — Path to the ssh command.
• -s [path] — Path to the oarnodesetting command.
• -p [path] — Path to the oarproperty command.
• -c [path] — Path to the oar.conf file.
• -D — Enables the debug mode for the parsing of hwloc's output. 🐛
• -h — Prints the command usage.

---

🔥 SEE ALSO 🔥

oarnodesetting(8), oarproperty(8), oar_resources_add(8), oarremoveresource(8), lstopo(1)

Go read those next, bestie, iykyk. 💜

---

🎀 COPYRIGHTS 🎀

Copyright 2003-2025 Laboratoire d'Informatique de Grenoble (http://www.liglab.fr). This software is licensed under the GNU General Public License Version 2 or above. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

---

okay that's the whole page, mwah 💖 this was oar_resources_init, page oar_resources_init(8), dated 2025-03-24. slay, go init some resources, you've got this 🫶✨