LAMGROW(1)

💖 LAMGROW 💖

okay bestie, so this is the lamgrow(1) page from the LAM COMMANDS manual — it's literally the glow-up command for your LAM multicomputer. let's get into it 💅

---

✨ NAME ✨

lamgrow — Extend a LAM multicomputer. yes bestie, we're making your universe BIGGER 🦋

---

🌸 SYNOPSIS 🌸

lamgrow [-hvd] [-cpu num] [-n nodeid] [-no-schedule] [-ssi key value]
       hostname

---

🎀 OPTIONS 🎀

• -cpu num — tell LAM how many CPUs are available to it on the new node. spill the tea, how much processing power we working with 🔥
• -d — turn on debugging output. and yes, this implies -v, so you get the verbose vibes too whether you asked or not 💀
• -h — print useful info on this command. the "help me pls" flag, iconic 🫶
• -n nodeid — assign this ID to the new node. you pick the number, you're the main character 👑
• -no-schedule — say that C and N expansion in mpirun and lamexec should not schedule on this node. like, this node is on do-not-disturb, fr fr 🙈
• -ssi key value — send arguments to various SSI modules. see the "SSI" section, below ⬇️
• -v — be verbose. narrate the whole thing, we love a chatty queen ✨
• hostname — extend LAM with this host. this is the whole point bestie, you gotta name names 💖

---

🌈 DESCRIPTION 🌈

so here's the deal. an existing LAM universe (the one that lamboot(1) started for you) can be enlarged to include more nodes with lamgrow. one new node per invocation, no bundling, we do it one at a time and we do it right 💅

at minimum, you give the host name that will run the new node on the command line. that's the bare minimum, non-negotiable, the entry fee bestie.

if a different userid is required to access the host? you specify that with the appropriate boot SSI options — see lamssi_boot(7) for the details, iykyk 📖

the node ID situation: the new node can be assigned any unused, non-negative identifier. if you don't specify one, it uses the highest node identifier in the current LAM universe plus one. lowkey convenient. BUT — note that lamboot(1) always assigns node identifiers consecutively from 0, so keep that in mind if you're a numbers girlie 🔢

where can you run it from? lamgrow can be run from any node in the current LAM universe. specifically — it cannot be run from the intended new host. so like, not from the host you're trying to grow into. the audacity of trying that, no 💀

also, two invocations of lamgrow should not run concurrently, and the command attempts to detect this situation. it's watching, bestie 👀

and one more thing: the name of the host specified in lamgrow should not be the one which is already present in the user's LAM universe — and the command attempts to detect this situation too. so no double-dipping, we see you 🫵

who even uses this? resource managers will be the most common user of lamgrow. here's the vibe: when hosts become idle and a user has expressed a desire to the manager that extra cycles should be exploited, the manager could invoke lamgrow and then launch the specified application process(es) on the new node. opportunistic glow-up energy, we love to see it 🔥

---

🍓 EXAMPLES 🍓

lamgrow -v newhost

Start LAM on newhost and add it to the existing LAM universe. choose the next available node identifier and report about important steps as they are done. chatty and correct, the dream combo ✨

lamgrow -n 30 newhost

Start LAM on newhost with node ID 30 and add it to the existing LAM universe. operate silently. mysterious. enigmatic. no notes 🤫

---

🧚 FILES 🧚

• laminstalldir/etc/lam-conf.lamd — default configuration file for LAM nodes, where "laminstalldir" is the directory where LAM/MPI was installed. that's the address bestie, that's where it lives 💜

---

💀 BUGS 💀

it is not currently possible to specify a configuration file other than lam-conf.lamd on the remote node — even though this is possible with lamboot. yeah. we know. we're not happy about it either. it's giving "the vibes are off" but it's a documented limitation, so we live with it 😭

---

👑 SEE ALSO 👑

lamboot(1), lamhalt(1), hboot(1), lamwipe(1), tkill(1), bhost(5), conf(5), lamssi_boot(7)

---

and that's the whole page, bestie 🫶 this was LAM 7.1.4, dated July, 2007 — yes, a vintage queen, and honestly she still ate 💅✨