Size: 432
Comment: upgrade comments
|
Size: 1761
Comment: notes on making rsync work
|
Deletions are marked like this. | Additions are marked like this. |
Line 18: | Line 18: |
= Tools = If you're SSH'd to the box, you can install/activate extra tools that you'd be used to having as a sysadmin. {{{ sudo synogear install }}} Despite being called with "install", all this does is drop you into a subshell with access to the tools, kinda like activating a python virtualenv. You'll need to run it any time you want to use them (or you can mess with your `$PATH` I guess). {{{ root@iowa:~# echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin root@iowa:~# synogear install root@iowa:~# echo $PATH /var/packages/DiagnosisTool/target/tool/:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin }}} = rsync over ssh = Maybe I broke it, but rsync doesn't work as expected without some fiddling. I thought it might be due to cruft in my `~/.bashrc` but I don't think it's that. This works though: {{{ rsync -avx --rsync-path=/usr/bin/rsync furinkan@iowa:/volume1/path/to/files/ /somewhere/local/or/whatever/ }}} The error message suggests it can't find or can't execute the rsync binary at the far end, but I can't tell why. {{{ furinkan@suomi:~$ ssh furinkan@iowa 'echo $PATH' /usr/bin:/bin:/usr/sbin:/sbin furinkan@suomi:~$ ssh furinkan@iowa 'which rsync' /usr/bin/rsync }}} |
Warspite
DS216j 2-bay basic model
2x 2TB SATA in SHR configuration, ext4 filesystem
At family's place
Iowa
DS916+ 4-bay advanced model with btrfs support
3x 6TB SATA in SHR configuration, btrfs filesystem, 1x SSD read-cache
At home
If I upgraded, I'd probably go for the DS1621+ so that I can add a 10gbps NIC. Alternatively, the DS1817 has onboard 10gig NICs but has no btrfs support or M.2 slots.
Tools
If you're SSH'd to the box, you can install/activate extra tools that you'd be used to having as a sysadmin.
sudo synogear install
Despite being called with "install", all this does is drop you into a subshell with access to the tools, kinda like activating a python virtualenv. You'll need to run it any time you want to use them (or you can mess with your $PATH I guess).
root@iowa:~# echo $PATH /sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin root@iowa:~# synogear install root@iowa:~# echo $PATH /var/packages/DiagnosisTool/target/tool/:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin
rsync over ssh
Maybe I broke it, but rsync doesn't work as expected without some fiddling. I thought it might be due to cruft in my ~/.bashrc but I don't think it's that.
This works though:
rsync -avx --rsync-path=/usr/bin/rsync furinkan@iowa:/volume1/path/to/files/ /somewhere/local/or/whatever/
The error message suggests it can't find or can't execute the rsync binary at the far end, but I can't tell why.
furinkan@suomi:~$ ssh furinkan@iowa 'echo $PATH' /usr/bin:/bin:/usr/sbin:/sbin furinkan@suomi:~$ ssh furinkan@iowa 'which rsync' /usr/bin/rsync