rclone / rclone/rclone

Ability to see progress when redirecting STDOUT

Open
#8,358 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
59.8k
Forks
5.4k
Avg merge
2d 14h
Merged PRs (30d)
48

Description

The associated forum post URL from https://forum.rclone.org

none

What is your current rclone version (output from rclone version)?

rclone v1.69.0

What problem are you are trying to solve?

I have a remote sftp site configured.
I am trying to capture the output of lsjson to get the details of all the remote files so that i can work on a duplicate file not being transferred (fyi im attempting to replicate over 1 million files from another remote system).

I am using --log-file to capture the logs and --progress to see the status - which works perfect on its own, however the output of lsjson is output to the stdout so the only way of capturing that information is to redirect stdout to a file in the console.

How do you think rclone should be changed to solve that?

Is there a way of outputting the progress information to the console and still redirect the output of lsjson to stdout/file?
I can think of two possible solutions:

  1. add something similar to --output-file to the ls* commands so that their output goes to the file but progress/errors still goes to stdout
  2. add the ability to redirect progress to stderr, that way a redirect in the console still captures the ls file output but i can still see the command progress in the console window
How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing an lsjson invocation with --progress, --log-file, and stdout redirected, then inspect the command's handling of progress and output streams. Done means one documented behavior cleanly separates lsjson output from visible progress or provides an output-file option, with the chosen behavior verified for this use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.