rsync.net has a restricted shell on the other side and apparently the df command isn't available. But at the very least, the exit code is coming back 1 and can be checked.
This is because you're sorting on the other side and the other side doesn't allow pipes. There's no need for that sort to be on the other side tho. Indeed, I just verified that if I pull the sort out of the ssh command, then it finds the latest backup.
Still doesn't find or create the inprogress link, so it is not continuing from the previously interrupted. Ah. Yes:
So, at this point, I'm guessing there are some things that can be changed to make it work a little more robustly (eg checking exit codes, doing minimal work on the remote side, etc), but I'm guessing this project just isn't a fit for rsync.net's restrictions.
P.S. Your Readme's TODO list is stale, considering the first bit that is failing is that FAT FS checker.
I just ran and finished a backup. To test, I ran it a second time:
rsync.net has a restricted shell on the other side and apparently the
df
command isn't available. But at the very least, the exit code is coming back1
and can be checked.Found some more:
This is because you're sorting on the other side and the other side doesn't allow pipes. There's no need for that sort to be on the other side tho. Indeed, I just verified that if I pull the sort out of the ssh command, then it finds the latest backup.
Still doesn't find or create the inprogress link, so it is not continuing from the previously interrupted. Ah. Yes:
So, at this point, I'm guessing there are some things that can be changed to make it work a little more robustly (eg checking exit codes, doing minimal work on the remote side, etc), but I'm guessing this project just isn't a fit for rsync.net's restrictions.
P.S. Your Readme's TODO list is stale, considering the first bit that is failing is that FAT FS checker.