10-29-2024, 09:57 PM
Sounds like some sort of permissions problem with the rclone binary especially since it's being run via ./rclone instead of just rclone.
I'm not sure how you installed it but typically it would be installed via standard apt like below and the binary would be in /usr/bin which is always in the global path so no need for specific path to it.
I'm not sure how you installed it but typically it would be installed via standard apt like below and the binary would be in /usr/bin which is always in the global path so no need for specific path to it.
Code:
pi@moode9:~ $ sudo apt -y install rclone
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
rclone
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 13.0 MB of archives.
After this operation, 57.2 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bookworm/main arm64 rclone arm64 1.60.1+dfsg-2+b5 [13.0 MB]
Fetched 13.0 MB in 2s (7,407 kB/s)
Selecting previously unselected package rclone.
(Reading database ... 84533 files and directories currently installed.)
Preparing to unpack .../rclone_1.60.1+dfsg-2+b5_arm64.deb ...
Unpacking rclone (1.60.1+dfsg-2+b5) ...######.............................................................................................................]
Setting up rclone (1.60.1+dfsg-2+b5) ...################################..................................................................................]
Processing triggers for man-db (2.11.2-2) ...#################################################################################............................]
pi@moode9:~ $
pi@moode9:~ $ which rclone
/usr/bin/rclone
pi@moode9:~ $