New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Options recover and max-lock missing in cmd/bisync/rc.go #7799
Comments
No real reason, other than that I just haven't gotten to it yet! (Those flags were added very recently.) There are a number of other rc params missing in addition to those two, and I started a branch to add them as well as some logic to differentiate between required and optional params, but just haven't had the time to finish it yet. Are you interested in working on it? I could send you what I started. In any case, thank you for opening this issue -- it's a good reminder that this still needs to be done! |
Since we are planning to adopt rclone, yes I am interested to collaborate too |
Here's what I started if you'd like to run with it! nielash@75c515f |
Hi all,
I was trying to integrate rclone into my system by using it as rcd server.
Noticed today there is no mappings for the options --recover and --max-lock on the api command sync/bisync
Checked cmd/bisync/rc.go and i'd say the implementation it's within my reach, just wondering if there is any particular reasons why some options are not mapped on the rc api?
Regards
The text was updated successfully, but these errors were encountered: