Re: [Sheflug] ftp large file upload problem

[Gary Stimson <bulk [at] xxxxxxxxxxxxxx>]

At 19:42 10/12/2003 +0000, you wrote:
> > Impossible.
> > Customer is synchronizing his archive with our ftp server and won't
> > rename files (already asked him :)) as there are too may of them already.
> > Denis.
John's filesize approach would generally work but, as he says, is 
hit-and-miss  because if the FTP dies half way then your second process 
jumps into life.
His idea of uploading to a different dir then renaming dirs sounds good, 
and shouldn't cause them too much hassle? (Might cause you some hassle 
since I assume the customer is using a FTP mirroring tool so the upload 
directory will need to exist and contain a copy of the most recent mirror).
The approach of reading the FTP server logs might help with this, though 
might be irritating to program and test.

Alternatively can the customer make a HTTP request to the server when the 
FTP is finished, triggering the second process? This is easy enough with 
the wget command (available for unixes and DOS).

Or just schedule the mirroring and second process to occur at certain times?

You've probably thought of all this, so I'll give up looking for 
alternative approaches now :-)   To answer your original question, AFAIK 
there's no way of keeping any existing file in place until the FTP upload 
of a replacement file has been successful, unless your FTP server has some 
special options for this.

Gary