Rsync Show Files Transferred
To make rsync show files transferred, enable verbose output or itemize changes during a run. This setting tells the tool to print every file name sent between hosts. Most teams run these file transfers over SSH using shared keys or broad server roles. When server permissions are too wide, anyone with login rights can pull or overwrite data. Local terminal logs do not stop bad transfers or record which user ran the job. How to make rsync show files transferred in workflows Rsync stays quiet by
Show Files Transferred: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To make rsync show files transferred, enable verbose output or itemize changes during a run. This setting tells the tool to print every file name sent between hosts. Most teams run these file transfers over SSH using shared keys or broad server roles. When server permissions are too wide, anyone with login rights can pull or overwrite data. Local terminal logs do not stop bad transfers or record which user ran the job.
How to make rsync show files transferred in workflows
Rsync stays quiet by default unless a transfer hits an error. The tool compares file sizes and timestamps between the source and target paths. It builds a list of differences before it sends any bytes over the network. When you enable verbose reporting, the tool prints each file path as it moves. You can also turn on summary statistics to see total byte counts and speeds.
For deeper checks, teams use itemized change output during a sync run. This mode shows why a file moved, such as a changed size or timestamp. It also flags permission updates, ownership changes, and new directories created on the host. Teams often pair this output with a dry run mode before making real changes. A dry run lists every file that would move without writing data to disk.
Why local transfer output leaves security gaps
Terminal output helps an engineer check that a script copied the right folder. Still, local screen text only exists in the window of the person running it. If a user forgets to redirect output to a log file, the record vanishes. Even when saved to a server file, anyone with root rights can delete it. Standard SSH keys also make it hard to tie a transfer to one person.
Native file sync setup decides who logs in, not what commands do in flight. Once an engineer opens an SSH session, they can copy sensitive folders anywhere. Local verbose settings cannot block a user from pulling database backups to a laptop. They also cannot mask sensitive fields like emails or card numbers inside synced files. Teams need centralized logs and command controls that sit outside the user terminal.
Show Files Transferred: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Best practices for auditing remote file syncs
Start by separating dry run checks from live production file transfers. Require engineers to review the planned file list before moving large data sets. Store transfer logs on a central log host rather than on the target machine. Central storage keeps the audit trail safe even if a server gets wiped.
Next, replace shared SSH keys with individual user identities for every server login. Scope file system roles so users only read or write the folders they need. Limit who can run sync jobs against production storage volumes during work hours. Combine itemized transfer logs with user identity records to build a complete audit trail.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev runs beside each supported service as an open-source proxy, a sidecar for your database or API.
First, hoop.dev guardrails block banned queries before they run. Then hoop.dev data masking rewrites matched sensitive values in responses in memory. The audit trail records every statement and verdict per resource. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
How can I see which files will transfer without moving them?
Enable dry run mode along with verbose output before starting the sync job. The tool scans both folders and prints the transfer list without writing any data.
Why does the output list directories when no files changed inside them?
The tool reports directory paths whenever it checks or updates folder timestamps and permissions. Using itemized change output shows whether actual file bytes moved or only metadata changed.
Where do file transfer logs go when a background script runs?
Background jobs discard screen output unless you configure a log file setting. You must set a log path in the job setup to save the file list.