Wildcard GET New File Behaviour
I have a script which runs periodically to move (copy and delete) all files from a remote directory (call it R) to a local one (call it L):
This task typically takes around 6 hours. If during the 6 hour duration a new file is added to R will GET get this too?
I imagine for wildcards GET does something like this:
If it works like this then that is great for my scenario, because I can gurantee new files won't be added when the script is started, but after that new files may well be. These files take several minutes to create, and I want to avoid WinSCP GETing a file which is partially written.
Can someone clarify how it works please?
get -delete -speed=2500 *.* L:\somefiles\
This task typically takes around 6 hours. If during the 6 hour duration a new file is added to R will GET get this too?
I imagine for wildcards GET does something like this:
- Get a list of the files in R.
- Loop through that list and transfer then delete each file.
If it works like this then that is great for my scenario, because I can gurantee new files won't be added when the script is started, but after that new files may well be. These files take several minutes to create, and I want to avoid WinSCP GETing a file which is partially written.
Can someone clarify how it works please?