Run:
- mount - it starts your mount with rc server listening to remote commands
rclone mount remote: mountPoint --rc --rc-addr 127.0.0.1:5572 --rc-no-auth
- initiate
vfs/refresh
- it outputs job ID - capture it and use in the next step
$ rclone rc vfs/refresh recursive=true --url 127.0.0.1:5572 _async=true
{
"jobid": 1
}
job/status
- it will tell you what is the status of your job id
still running as you can see "finished": false
:
$ rclone rc --url 127.0.0.1:5572 --json '{ "jobid":1}' job/status
{
"duration": 0,
"endTime": "0001-01-01T00:00:00Z",
"error": "",
"finished": false,
"group": "job/1",
"id": 1,
"output": null,
"startTime": "2023-11-06T20:33:39.455784Z",
"success": false
}
checking, checking until finished - until "finished": true
and all other details:
$ rclone rc --url 127.0.0.1:5572 --json '{ "jobid":1}' job/status
{
"duration": 160.298011965,
"endTime": "2023-11-06T20:36:19.752927Z",
"error": "",
"finished": true,
"group": "job/1",
"id": 1,
"output": {
"result": {
"": "OK"
}
},
"startTime": "2023-11-06T20:33:39.455784Z",
"success": true
}
You have to check job status within 60s before it is done - as then job status will be purged.
You can change it if not enough time using --rc-job-expire-duration flag when you start you rc server (in rclone mount
command)
You have basics working already - now time to give it some sophistication:)
Also to give you some benchmark you can see that my vfs/refresh
job finished in 160 seconds - it is for remote with 500k files - this is why I consider Proton painfully slow.