I doubt it is faster method than using the one that works and will complete the operation rather than shut the machine down doing it the other way. Then you need to fire it up some time later and do it all again. Your description of the problem here has nothing to do with ssh and no amount of configuration settings will change that. Your machine has for some reason decided it will not run properly when it shuts itself down, my pi which I just updated today with the new point release had been running since the last time the kernel was upgraded and required a reboot, according to the date on the files in /boot that was May 3 roughly fifty-eight days ago.I run the rsync with -P because I like to see the progress so I know when it is done before I shut the server off. What happens is, after a couple of hours, my server shuts off the connection to the terminal on my client due to "inactivity" and I no longer see any progress. Oh and I am not syncing from client to server, I am backing up files from a USB stick on the server to its RAID (find it faster than sending it over the network). If you are sending files over the network that will keep it alive no problem!
Code:
zeus@bullseye-raspi:~$ ls -l /boot/total 107100-rw-r--r-- 1 root root 253957 May 3 09:40 config-5.10.0-29-arm64-rw-r--r-- 1 root root 253957 Jun 1 06:24 config-5.10.0-30-arm64drwxr-xr-x 2 root root 16384 Dec 31 1969 firmware-rw-r--r-- 1 root root 27157759 May 11 11:37 initrd.img-5.10.0-29-arm64-rw-r--r-- 1 root root 27163299 Jul 1 19:03 initrd.img-5.10.0-30-arm64-rw-r--r-- 1 root root 83 May 3 09:40 System.map-5.10.0-29-arm64-rw-r--r-- 1 root root 83 Jun 1 06:24 System.map-5.10.0-30-arm64-rw-r--r-- 1 root root 27402176 May 3 09:40 vmlinuz-5.10.0-29-arm64-rw-r--r-- 1 root root 27402176 Jun 1 06:24 vmlinuz-5.10.0-30-arm64
Statistics: Posted by RedGreen925 — 2024-07-02 03:31