LAMNODES(1)

πŸ’– NAME πŸ’–

lamnodes β€” bestie, this one resolves LAM node/CPU notation into actual Unix hostnames. no cap. ✨


πŸŽ€ SYNOPSIS πŸŽ€

lamnodes [-chin] [where]

✨ OPTIONS ✨

  • -c β€” hush the CPU count for each node, don't print it.
  • -h β€” print the command help menu, iykyk.
  • -i β€” print IP addresses instead of IP names. switching it up fr fr.
  • -n β€” suppress printing CPU count for each node. like -c but, you know, -n. πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so. the lamnodes command takes LAM's whole node/CPU nomenclature situation and resolves it into Unix hostnames. that's the vibe. it can also be your little detective for figuring out the current running configuration of the LAM/MPI run-time environment, and for generating a boot schema you can use to launch LAM later on. very main character energy honestly. πŸ‘‘

by default, lamnodes prints out the node number, default IP name, CPU count, and per-node flags for every node in the running LAM. gethostbyaddr(3) is what grabs the default hostnames for you. and if gethostbyaddr(3) fails? no worries bestie, it just displays the IP number instead. πŸ’…

setup shell scripts (and the like) can totally use this command to pull info out of a currently-running LAM universe. for example, use lamnodes to resolve particular CPUs and/or nodes to specific unix hostnames. and in a batch environment, lamnodes can tell you which CPUs share a common node β€” note that MPI_GET_PROCESSOR_NAME can be used for a similar effect inside an MPI program. slay. 🌸

lamnodes also shows per-node flags. currently defined flags are:

  • origin β€” the node where lamboot was executed.
  • this_node β€” the node where lamnodes is running. that's the one you're on, bestie. πŸ“
  • no_schedule β€” this node will not be used to run MPI and serial processes when N and C are used to mpirun and lamexec.

🌈 EXAMPLES 🌈

  • lamnodes N -n display IP names and CPU counts for all nodes. this output can be saved and later used with lamboot(1). iconic.
  • lamnodes C -n -c display the IP name of the nodes containing each CPU, and suppress the LAM node number and CPU count. this output can be saved and later used with lamboot(1). obsessed. ✨

πŸ”₯ SEE ALSO πŸ”₯

bhost(5), gethostbyaddr(3), lamboot(1)


ngl, this page is giving LAM 7.1.4, dated July, 2007, straight outta the LAM TOOLS corner of the group chat. periodt. πŸ’–πŸ«Ά