IREG(1)

πŸ“¦ version 5.0.2, in nixos 26.05

πŸŽ€ NAME πŸŽ€

okay so this is ireg β€” an iRODS iCommand, and it lives on the IREG(1) User Commands manual page. bestie, we're registering files into iRODS, and yes it's a whole vibe πŸ’–

✨ SYNOPSIS ✨

ireg [-hfrkKvV] [--repl] [-D dataType] [-R resource]

πŸ’– DESCRIPTION πŸ’–

physicalFilePath, irodsPath

Register a file or a directory of files and subdirectory into iRODS. The file or the directory of files must already exist on the server where the resource is located. The full path must be supplied for both the physicalFilePath and the irodsPath. no shortcuts, bestie 😌

With the -r option, the entire content beneath the physicalFilePath (files and subdirectories) will be recursively registered beneath the irodsPath. For example, the command:

ireg -r /tmp/src1 /tempZone/home/myUser/src1

grafts all files and subdirectories beneath the directory /tmp/src1 to the collection /tempZone/home/myUser/src1. slay πŸ¦‹

By default, only rodsAdmin users are allowed to register files or directories. More permissive registration policies can be set in the server's rule base using the acNoChkFilePathPerm() rule.

bestie PSA 🚨 It is considered best practice for the target resource be a single local storage resource. A side effect of not following this best practice could be unwanted extra replicas of a mounted collection or other structured file. Registered files should be well-understood by the administrator so the line between iRODS-managed data and user-managed data can be properly maintained. iykyk πŸ’…

✨ Options are: ✨

  • -R β€” resource β€” specifies the target storage resource. This can also be specified in your environment or via a rule set up by the administrator.
  • -r β€” recursive β€” recursively register all directories and files in physicalFilePath.
  • -f β€” Force. If the target collection already exists, register the files and subdirectories that have not already been registered in the directory.
  • -k β€” calculate a checksum on the iRODS client and store with the file details.
  • -K β€” calculate a checksum on the iRODS server and store with the file details.
  • --repl β€” register the physical path as a replica.
  • --exclude-from filename β€” don't register files matching patterns contained in the specified file. The file must be readable on the server where the resource is located and must be an absolute pathname.
  • -v β€” verbose.
  • -V β€” Very verbose.
  • -h β€” this help.

oh and real talk: the synopsis also has -D dataType β€” the original options list doesn't give it its own description, so I'm not inventing one, iykyk πŸ’€


okay that's the page, bestie 🫢 β€” this ireg is from iRODS Version 5.0.2, the source/version footer is ireg iRODS-5.0.2, the date is January 1980, and the manual page is IREG(1). periodt πŸ’…

πŸ“¦ where this page comes from