chirp_stream_files(1)

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

πŸ’– chirp_distribute β€” the manual page, but make it cute πŸ’–

okay bestie, so this is chirp_stream_files(1) from the Cooperative Computing Tools, and the star of the show inside it is chirp_distribute. sit down, grab a boba, we're gonna replicate some directories 🌸


✨ NAME ✨

chirp_distribute β€” copy a directory from one Chirp server to one or more Chirp server(s). that's it, that's the vibe πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

chirp_distribute [options] <sourcehost> <sourcepath> <host1> <host2> <host3> ...

like, give it a source and then a whole little army of destinations. iconic behavior honestly πŸ‘‘


πŸ’… DESCRIPTION πŸ’…

chirp_distribute is the tool for coping commonly used data across Chirp servers. the data starts its journey on a Chirp server at <sourcehost> <sourcepath>, and then it gets copied out to a list of Chirp server(s) β€” <host1> <host2> <host3>, etc … β€” and it just keeps going, no cap πŸ’«

it's the quick-and-simple way to replicate a directory from one Chirp server to many Chirp servers: it builds a spanning tree, then transfers data concurrently from host to host using third party transfer. and the way that it's faster than manually copying data using parrot cp, chirp_put or chirp_third_put?? obsessed. literally ate and left no crumbs πŸ”₯

and pookie, it can also clean up replicated data β€” that's what the -X option is for 🧹✨


🌈 OPTIONS 🌈

  • -a, --auth=<flag> β€” require this authentication mode. no flag, no entry πŸ”
  • -d, --debug=<flag> β€” turn on debugging for this subsystem. for when you wanna see everything πŸ‘€
  • -D, --info-transfer β€” show detailed location, time, and performance of each transfer. receipts for every single copy πŸ’…
  • -F, --failures-file=<file> β€” write the matrix of failures to this file. so if something flops, you have it written down 😭
  • -i, --tickets=<files> β€” a comma-delimited list of tickets to use for authentication. bring your tickets bestie 🎟️
  • -N, --copies-max=<num> β€” stop after this number of successful copies. like, we're done here βœ‹
  • -p, --jobs=<num> β€” maximum number of processes to run at once (default=100). multitasking queen πŸ‘―
  • -R, --randomize-hosts β€” randomize the order of the target hosts given on the command line. chaos mode, but make it efficient 🎲
  • -t, --timeout=<time> β€” timeout for for each copy. (default is 3600s) ⏰ (yes, the "for for" is the original's, we don't touch the facts)
  • -T, --timeout-all=<time> β€” overall timeout for the entire distribution. (default is 3600). the whole operation has a curfew πŸ•›
  • -v, --verbose β€” show program version. πŸ’¬
  • -X, --delete-target β€” delete data from all of the target hosts. the cleanup era πŸ—‘οΈβœ¨
  • -Y, --info-success β€” show confirmation of successful placements. validation!! we love to see it 🫢
  • -h, --help β€” show help text. when in doubt, ask πŸ₯Ί

🌸 ENVIRONMENT VARIABLES 🌸

  • CHIRP_CLIENT_TICKETS β€” comma delimited list of tickets to authenticate with (same as -i). πŸŽŸοΈπŸ’–

⭐ EXIT STATUS ⭐

on success, returns zero. on failure, returns non-zero. slay or flop, there is no in-between πŸ’€


πŸ¦‹ EXAMPLES πŸ¦‹

copy a directory from server1 to server2, server3, server4 using chirp_distribute:

chirp_distribute server1.somewhere.edu /mydata server2.somewhere.edu server3.somewhere.edu server4.somewhere.edu

replicate a directory from server1 to all available Chirp server(s) in the Chirp catalog using chirp_distribute and chirp_status:

chirp_distribute server1.somewhere.edu /mydata `chirp_status -s`

replicate a directory from server1 to all available Chirp server(s) in the Chirp catalog using chirp_distribute and chirp_status. however, stop when you reach 100 copies with the -N option:

chirp_distribute -N 100 server1.somewhere.edu /mydata `chirp_status -s`

clean up replicated data using chirp_distribute using the -X option:

chirp_distribute -X server1.somewhere.edu /mydata `chirp_status -s`
note bestie: those backticks around chirp_status -s are doing real shell magic β€” the shell runs chirp_status -s first and drops its output right into your command. it's giving command substitution main character energy 🧚

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. πŸ“œπŸ’œ


πŸ’œ SEE ALSO πŸ’œ


and that's the whole page, bestie 🫢 this one's from CCTools 8.0.0 DEVELOPMENT β€” go replicate something gorgeous, ily, bye!! βœ¨πŸ’–πŸŽ€

πŸ“¦ where this page comes from