chirp(1)

✨ chirp(1) ✨

okay bestie, gather round πŸ’– this is chirp, part of the Cooperative Computing Tools β€” and she's the command line tool that gives you explicit control of a Chirp server. like, full control. main character energy, no cap πŸ‘‘


🌸 SYNOPSIS 🌸

chirp [options] [hostname] [command]

πŸ¦‹ DESCRIPTION πŸ¦‹

so chirp is your little tool for connecting to and managing a Chirp server, kinda like how an FTP client does it. you can hop onto a Chirp server, copy files around, manage directories, audit nodes, all of it. it's giving ✨remote file system bestie✨.

here are the important chirp commands, and yes you need to know all of them 🫢:

  • open <host> β€” connect to a Chirp server.
  • close β€” close the connection to the current Chirp server.
  • get <remotefile> [localfile] β€” copy a remote file down to local storage.
  • put <localfile> [remotefile] β€” copy a local file up to the Chirp server.
  • thirdput <file> <3rdhost> <3rdfile> β€” copy a remote file to another Chirp server. third-party realness πŸ’…
  • getacl <remotepath> β€” get the acl of a remote file/directory.
  • setacl <remotepath> <user> <rwldax> β€” set the acl for a remote file/directory.
  • ls [-la] [remotepath] β€” list the contents of a remote directory.
  • mv <oldname> <newname> β€” change the name of a remote file.
  • rm <file> β€” delete a remote file.
  • audit [-r] β€” audit the current Chirp server.
  • exit β€” close the connection and exit Chirp.

chirp also manages Chirp tickets for authentication purposes, and honestly? iconic πŸ”₯

  • ticket_create [-o[utput] <ticket filename>] [-s[ubject] <subject/user>] [-d[uration] <duration>] [-b[its] <bits>] [[<directory> <acl>] ...] β€” create a ticket.
  • ticket_register <name> [<subject>] <duration> β€” manually register a ticket with multiple Chirp servers.
  • ticket_delete <name> β€” remove a ticket.
  • ticket_list <name> β€” list registered tickets on a Chirp server.
  • ticket_get <name> β€” check the status of a ticket.
  • ticket_modify <name> <directory> <aclmask> β€” modify a ticket.

πŸ’… OPTIONS πŸ’…

  • -a, --auth=<flag> β€” require this authentication mode. no vibes-checking past this point, bestie.
  • -d, --debug=<flag> β€” enable debugging for this subsystem.
  • -i, --tickets=<files> β€” comma-delimited list of tickets to use for authentication.
  • -l, --verbose β€” long transfer information. she's chatty and we love that for her.
  • -t, --timeout=<time> β€” set the remote operation timeout.
  • -v, --version β€” show the program version.
  • -h, --help β€” show the help text.

🌈 ENVIRONMENT VARIABLES 🌈

  • CHIRP_CLIENT_TICKETS β€” comma delimited list of tickets to authenticate with. literally the exact same thing as -i, just ambient ✨

⭐ EXIT STATUS ⭐

on success, returns zero. on failure, returns non-zero. that's the whole vibe check 😌


πŸŽ€ EXAMPLES πŸŽ€

to connect to a Chirp server using chirp:

% chirp server1.somewhere.edu
chirp> (enter more commands here)

to copy a single local file using chirp:

% chirp server1.somewhere.edu put /tmp/mydata.dat /mydata/mydata.dat

to get a single remote file using chirp:

% chirp server1.somewhere.edu get /mydata/mydata.dat /tmp/mydata.dat

to create a ticket using:

% chirp server1.somewhere.edu get ticket_create -output myticket.ticket -subject unix:user -bits 1024 -duration 86400 / rl /foo rwl

to register a ticket with other Chirp servers:

% chirp server2.somewhere.edu ticket_register myticket.ticket unix:user 86400

to delete a ticket:

% chirp server1.somewhere.edu ticket_delete myticket.ticket

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. protect the license bestie, it's the law 🫢


πŸ‘‘ SEE ALSO πŸ‘‘


and that's the whole page, bestie!! πŸ¦‹βœ¨ this was CCTools 8.0.0 DEVELOPMENT, the chirp(1) era β€” go forth and manage your servers, you absolute legend πŸ’œπŸŽ€

πŸ“¦ where this page comes from