Ensure ‘Enable backup rsync service’ is enabled in your Ugreen Control Panel, and select an existing user that will be used when transferring with rsync:
Note that instead of using the path of a folder on a volume, e.g. /volume1/folder, if folder is the name of the share, use this as the target path without any absolete path prefix.
This is hinted at in this post, and while it seems to differ from how you’d normally specify a remote destination, this is how rsync on a Ugreen appears to work.
As part of moving from one hosting provider to another, I needed to move a large amount of uploaded files to my local machine and then out to a VM on a new provider. Looking at rsync to do this, for moving the content locally first I didn’t want to eat up all my home bandwidth, so found there is a ‘bwlimit’ parameter in KB, e.g. –bwlimit=500 would limit to 500kbps:
rsync --bwlimit=[bw here in kbps] -a --progress [id]@[host]:/source/path .
Run this from the folder where you want the files to arrive what also contains folder ‘path’ (otherwise you’ll end up with path/path/[files here])
zsh on MacOS saves your terminal history to ~/.zsh_history
If you entered a command that you don’t want to remain in your history, edit the file and delete the lines you don’t want to remain in your history, then save. Exist terminal and reopen.
In my previous post, I said I was going to test my two serial cables with every serial device I have to work out which combination worked and which didn’t to find out what the difference was. It didn’t take long to realize though that the DB25 to DB25 serial cable I have that I assumed was a null modem cable only worked with certain types of connections.
For example, it only worked with a VT terminal to a modem type device (in this case a PK-232 packet radio TNC), but not terminal to PC. In the first case that is a DTE to DCE type connection (which worked), whereas the second is DTE to DTE (which didn’t).
A DTE to DCE connection requires a straight through cable
A DTE to DTE requires a crossover connection (tx to rx, rx to rx)
This realization pretty much confirmed that the cable that was only working for DTE to DCE connectors was a straight through cable, and explained why it didn’t work elsewhere.
Long story short, I picked up a cheap null modem adapter that does the crossover for you, converting a straight through cable to a crossover:
From left to right:
USB serial dongle, connected to the Pi
DB9 to DB25 converter
DB25 to DB25 null model adapter
DB25 to DB25 straight through (converted to crossover with the null modem adapter)
And now I can successfully get a terminal logon to my Raspberry Pi:
To enable the serial terminal login via ttyUSB0, see this post.
