DMTCP_...DINATOR(1)

πŸ’– DMTCP_...DINATOR(1) β€” Distributed MultiThreaded CheckPointing, section 1 πŸ’–

okay bestie, so this is the manual page for DMTCP_...DINATOR, section 1 of the Distributed MultiThreaded CheckPointing manuals. it's the coordinator. it's the main character. it literally runs the group chat for all your checkpointing processes. let's get into it πŸ’…


✨ NAME ✨

dmtcp_coordinater β€” coordinates checkpoints among multiple processes.

ngl the NAME line spells it dmtcp_coordinater and the DESCRIPTION spells it dmtcp_coordinator. i am not fixing it. i am reporting it faithfully. both spellings are iconic in their own way 🫢

🌸 SYNOPSIS 🌸

dmtcp_coordinater [OPTIONS]

that's it. that's the whole vibe check. just run it with whatever options you need. periodt.


πŸ¦‹ DESCRIPTION πŸ¦‹

dmtcp_coordinator coordinates checkpoints among multiple processes.

that's literally the whole thing she does. she's the one keeping everyone in sync when it's checkpoint o'clock. the way that she just coordinates? obsessed. πŸŽ€


✨ OPTIONS ✨

  • -p, --coord-port port β€” the port to listen on. also settable via the environment variable DMTCP_COORD_PORT. default is 7779 πŸ’–
  • --port-file filename β€” a file where she'll write the listener port number. super useful with --coord-port 0, which is the move when you want a random port assigned, no cap.
  • --ckptdir path β€” the directory where dmtcp_restart_script.sh gets stored. env var: DMTCP_CHECKPOINT_DIR. default: ./ (yes, literally just where you're standing 🫢)
  • --tmpdir path β€” the directory for temporary files. env var: DMTCP_TMPDIR. default is the env var TMDPIR β€” yes, that's the spelling in the original, TMDPIR, not TMPDIR β€” or /tmp if that's not set.
  • --exit-on-last β€” she bails automatically when the last client disconnects. last one out, lights off, bye πŸ’€
  • --exit-after-ckpt β€” she bails automatically once the checkpoint is created.
  • --daemon β€” runs silently in the background after detaching from the parent process. lowkey. quiet. lurking. 🧚
  • -i, --interval <val> β€” time in seconds between automatic checkpoints. env var: DMTCP_CHECKPOINT_INTERVAL. default: 0, which means disabled β€” no auto-checkpoints unless you ask.
  • -q, --quiet β€” skips the copyright notice. for when you're too cool for legal text (but the legal text still applies, bestie πŸ‘‘).
  • --help β€” prints this message and exits. the classic.
  • --version β€” prints version information and exits.

πŸŽ€ Commands for Coordinator πŸŽ€

so when she's running, you can just type these little letters at her like you're texting your bestie:

  • l β€” list connected nodes
  • s β€” print status message
  • c β€” checkpoint all nodes
  • i β€” print current checkpoint interval
    • (to change the checkpoint interval, use dmtcp_command, not this. iykyk)
  • k β€” kill all nodes
  • q β€” kill all nodes and quit
  • ? β€” show this message

🌈 REPORTING BUGS 🌈

found a bug? don't suffer in silence, tell the group chat:


πŸ’œ SEE ALSO πŸ’œ

dmtcp(1), dmtcp_coordinator(1), dmtcp_launch(1), dmtcp_restart(1), dmtcp_command(1)

(the whole friend group. go read them all. πŸ’–)


πŸ‘‘ AUTHOR πŸ‘‘

see /usr/share/doc/dmtcp-3.0.0/AUTHORS.


⭐ VERSION ⭐

DMTCP version 3.0.0 of November, 2017.


see the /usr/share/doc/dmtcp-3.0.0/COPYING file.

License LGPLv3+: GNU LGPL version 3 or later <http://gnu.org/licenses/lgpl.html>.

🚨 this program comes with ABSOLUTELY NO WARRANTY. it is free software, and you are welcome to redistribute it under certain conditions; see the COPYING file for details. read the fine print bestie, it's giving responsible queen energy πŸ’…

and that's the whole page, bestie!! πŸŽ€βœ¨ this one came from the Distributed MultiThreaded Che... page, dated November, 2017, sitting right up in DMTCP_...DINATOR(1) β€” go forth and coordinate, you've got this πŸ¦‹πŸ’–

πŸ“¦ where this page comes from