Which defeats the purpose of having the copy process run entirely from the My Cloud without the need for a computer. In my case if I kill the WinSCP application the copy stops entirely when copying from the My Cloud to a USB hard drive attached to the My Cloud. If I leave a separate SSH session running that means I have to leave both the WinSCP (default settings) and the PC running. WinSCP is a good program but does have some limitations.
Its a fundamental problem if one wants to run management tasks on the My Cloud without involving an app or program on the computer and application that must be left running the whole time. At least by using the scripting method previously mentioned (nohup) one can kill the application and turn off the computer and the copy process (or what ever process one initiated using nohup) will continue to run on the My Cloud. Its not perfect but does accomplish what some are seeking, having a copy process that runs independent of the computer or software on that computer once that process is initiated on the My Cloud.
Example nohup rsync command on a first gen v4.x single bay My Cloud to copy all MP4 files from a directory on the My Cloud to a USB hard drive attached to that My Cloud’s USB port. Command can be issued from SSH clients like Putty or WinSCP and those programs can be closed while the copy process continues on the My Cloud.
nohup rsync /DataVolume/shares/Public/*.mp4 /var/media/Toshiba_Canvio_1TB/
There may be ways to create a custom command within WinSCP to automate the use of nohup to copy files using WinSCP.
Edit to add: Since WinSCP won’t show the results of top properly (live) here is the results of top run from Putty showing the rsync process continuing in the background on the My Cloud after WinSCP was closed/shutdown after triggering the nohup rsync command via the WinSCP terminal window.
