Install xrootd with Homebrew, apt, dnf, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• cconfig
• cmsd
• frm_admin
• frm_purged
• frm_xfragent
• frm_xfrd
• mpxstats
• wait41
• xrdacctest
• xrdadler32
• xrdcks
• xrdcopy
• xrdcp
• xrdcrc32c
• xrdfs
• xrdgsiproxy
• xrdgsitest
• xrdmapc
• xrdpfc_print
• xrdpinls
• xrdpwdadmin
• xrdreplay
• xrdsssadmin
• xrootd
• xrootd-config

Project history

The official XRootD site and README trace the project to the High Energy Physics community's need to satisfy the BaBar experiment's data storage and access requirements at SLAC. It was later extended for Large Hadron Collider experiments at CERN, where the same design pressures became much larger: remote access, federated storage, fault tolerance, and throughput at scientific scale.

The name expands to eXtended ROOT Daemon, reflecting its ROOT/HEP origins, but the modern project is broader than a single experiment or file format. The current documentation describes a scalable architecture with multi-protocol communications, plugins, authentication and authorization methods, erasure-coded files, and integration with storage systems such as Ceph.

Adoption history

XRootD became infrastructure for the Worldwide LHC Computing Grid era because LHC experiments needed data access that could span institutes, national labs, and storage technologies. The official README states that XRootD powers CERN's EOS distributed filesystem, which is used by LHC experiments and backs CERNBox.

Adoption moved beyond one site through distribution channels and ecosystem bindings. The project documents installation via RPM and DEB repositories, distro packages, Homebrew, conda-forge, and PyPI bindings, which reflects how XRootD serves both storage administrators and analysis users who only need clients such as `xrdcp` or Python bindings.

How it is used

Administrators deploy XRootD servers and cluster-management components to expose distributed storage, configure authentication, proxying, monitoring, federation, and backend storage plugins. The package includes daemons such as `xrootd` and `cmsd` plus many administrative and diagnostic commands.

Data users most often encounter the client side: `xrdcp` for copying files, `xrdfs` for filesystem-like operations, checksum tools, Python bindings, and experiment frameworks that open files remotely through the XRootD protocol rather than first staging full datasets locally.

Why package nerds care

XRootD is one of the clearest examples of scientific infrastructure hidden behind a package name. Installing it may provide a single CLI for a laptop user, but the same source tree also underpins globally federated data access for particle-physics workloads.

It matters to package nerds because it packages a protocol ecosystem: daemons, client commands, C++ libraries, Python bindings, config grammar, docs, and site policies all have to line up across long-lived Linux distributions, macOS workstations, and scientific clusters.

Timeline

• Early 2000s: XRootD is initially developed in the HEP community for BaBar data access at SLAC.
• LHC era: The project is extended for Large Hadron Collider experiment data access at CERN.
• 2010s: XRootD becomes part of WLCG-style federated data access and storage operations.
• 2020: XRootD 5.x documentation and package channels support modern client/server deployments.
• 2026: XRootD 6.x releases and documentation continue, with official packages and bindings across RPM, DEB, Homebrew, conda-forge, and PyPI.

Related projects

• ROOT is the original high-energy-physics data ecosystem behind the XRootD name.
• EOS is CERN's distributed filesystem powered by XRootD technology.
• CERNBox uses EOS, and therefore indirectly depends on XRootD as storage infrastructure.
• Ceph is a storage system XRootD can integrate with through plugins or deployments.
• WLCG data-management tooling commonly uses XRootD clients and third-party copy workflows.

Sources

• https://cds.cern.ch/record/2919257/files/document.pdf
• https://github.com/xrootd/xrootd
• https://raw.githubusercontent.com/xrootd/xrootd/master/README.md
• https://xrootd.org/
• https://xrootd.org/docs.html