catalog_update(1)

πŸ“¦
version 9.9 Β· 3 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’– catalog_update(1) β€” the send-an-update-to-the-catalog-server girlie πŸ’–

okay so bestie, you know how the catalog server is out here collecting gossip about every host in the cluster? yeah. this is the tiny little hand-held megaphone you use to slide into its DMs yourself. it lives in the Cooperative Computing Tools manual, and no cap, it's short but it serves. 🫢


✨ NAME ✨

catalog_update β€” send update to catalog server

that's it. that's the whole name section. she's lowkey humble. πŸ’…


🌈 SYNOPSIS 🌈

catalog_update [options] [name=value] ..

πŸ¦‹ DESCRIPTION πŸ¦‹

so the catalog_update tool lets you manually yeet an update to a catalog server via a short UDP packet. that's the vibe. one little packet, one big glow-up for the catalog. ✨


πŸŽ€ OPTIONS πŸŽ€

  • -c, --catalog=<host> β€” send the update to this catalog host. this is your target. your main character server. πŸ‘‘
  • -f, --file=<json-file> β€” send extra JSON attributes that live in this file. more fields, more lore. πŸ“„
  • -d, --debug=<flags> β€” turn on debug flags.
  • -o, --debug-file=<file> β€” send that debug output to this file instead of wherever it was going.
  • -v <version> β€” show software version. version check, periodt. ⭐
  • -h <help> β€” show all options. when in doubt, ask for help, it's giving self-care. πŸ™ˆ

the catalog_update tool sends a custom message to the catalog server in the form of a JSON object with various properties describing the host. by default, the catalog_update tool includes the following fields in the update:

  • type β€” this describes the node type (default is "node").
  • version β€” this is the version of CCTools.
  • cpu β€” this is CPU architecture of the machine.
  • opsys β€” this is operating system of the machine.
  • opsysversion β€” this is operating system version of the machine.
  • load1 β€” this is 1-minute load of the machine.
  • load5 β€” this is 5-minute load of the machine.
  • load15 β€” this is 15-minute load of the machine.
  • memory_total β€” this is total amount of memory on the machine
  • memory_avail β€” this is amount of available memory on the machine
  • cpus β€” this is number of detected CPUs on the machine.
  • uptime β€” this how long the machine has been running.
  • owner β€” this is user who sent the update.
okay so about the field name β€” it is intended to give a human-readable name to a service or application which accepts incoming connections at port. that's the tea, fr fr. πŸ“

🌸 ENVIRONMENT VARIABLES 🌸

  • CATALOG_HOST β€” hostname of catalog server (same as -c). set it once, forget it, live your life. πŸ’œ

πŸ’€ EXIT STATUS πŸ’€

  • on success, returns zero. πŸŽ‰
  • on failure, returns non-zero. 😭

🧚 EXAMPLES 🧚

the following example sends an update to the catalog server located at catalog.cse.nd.edu with three custom fields. watch her work:

% cat > test.json << EOF
{
    "type" : "node",
    "has_java" : true,
    "mode" : 3
}
EOF
% catalog_update -c catalog.cse.nd.edu -f test.json

look at that. iconic. ate. no crumbs. πŸ”₯


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.

yes bestie, read the license, it's not optional. respecting licenses is highkey the most main character energy there is. πŸ’…

πŸ’– SEE ALSO πŸ’–


and that's the whole page, bestie!! πŸŽ€ this was CCTools 8.0.0 DEVELOPMENT, mwah, go send some updates and slay. πŸ¦‹βœ¨πŸ’–

πŸ“¦ where this page comes from