/etc/filetrace/config.toml and the filetrace-agent service for systemd, OpenRC or SysV init. The programs are linked statically, so one build runs on any distribution.
Requirements
SELinux in enforcing mode is untested. Run
filetrace doctor after installing to see what the kernel accepts.
Install with the installer script
On Linux, the installer detects the package manager (apt, dnf, yum, zypper or apk), adds the Filetrace repository with its signing key, and installs thefiletrace package, so upgrades arrive with the system’s own. Where none of these package managers is present, it downloads the release archive, checks it against the release’s SHA256SUMS, unpacks it under /usr/local and installs the service for the init system it finds.
-s --:
The environment variables
FILETRACE_VERSION, FILETRACE_CHANNEL and FILETRACE_NO_START=1 stand for the options of the same name.
The installer starts the agent unless
--no-start is given. With the agent running as root, the commands that query it need sudo.Install from a package repository
The repositories live underhttps://filetrace.eorlov.org and carry the stable and lts channels. apt and yum metadata and the rpm packages are signed with the OpenPGP key at https://filetrace.eorlov.org/gpg.key; the apk repository and packages with the RSA key at https://filetrace.eorlov.org/apk/filetrace.rsa.pub. Security lists their fingerprints.
- Debian and Ubuntu
- Fedora and RHEL
- openSUSE
- Alpine
filetrace-agent when it is first installed.lts channel, replace stable with lts in the suite, baseurl or repository URL.
Install with Homebrew
Homebrew installs the two programs on macOS 15 or later and on Linux, without a service.filetrace follows the newest release. To stay on one release line, install its formula instead, for example orlovevgeny/filetrace/filetrace@26.11.
Install from a release archive
Every release carries archives for Linux and macOS, also available athttps://filetrace.eorlov.org/dist/<tag>/. An archive holds bin/filetrace and bin/filetrace-agent, the default configuration and the service definitions. Check an archive against the release’s SHA256SUMS, or verify its build attestation:
Verify the installation
filetrace version prints the version, build and platform, and whether the agent is running. filetrace doctor reports whether the kernel can be monitored; it exits with 0 when the status is READY.
Upgrade
Upgrades arrive through the package manager like any other package. The command and the agent speak one protocol version, so an upgrade restarts a running agent. If/etc/filetrace/config.toml is not valid for the new version, the agent is not restarted and the package manager prints what filetrace config validate reports. An upgrade never overwrites the configuration file.
With an archive installation, run the installer again. It replaces the programs and restarts a running agent under the same condition: the configuration must be valid for the new version.
Uninstall
/etc/filetrace is left in place. To remove a package installed by hand, use the package manager: apt remove filetrace, dnf remove filetrace, zypper remove filetrace or apk del filetrace.