Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re^2: Monitoring an FTP upload directory

by wjw (Priest)
on Nov 07, 2006 at 21:25 UTC ( #582735=note: print w/replies, xml ) Need Help??

in reply to Re: Monitoring an FTP upload directory
in thread Monitoring an FTP upload directory

We had also had the problem of cutomers uploading more than once. The files they uploaded were very large (50-60 meg) so they would start a transfer, go away for a while and come back noting that the file was not there and disregarding the fact that their client showed a successful transfer, then start the whole thing over again.

We addressed that problem by actually placing a text file in the upload directory which had a name like (file_name)xfer_complete.txt. The contents of the file were always the same; something like "your file has been recieved and moved to a secure place on our network" if I recall correctly.

Most customers caught on right away, the others we would 'coach' if we noticed they needed it. We removed these files after a few hours, and our scp script was coded to ignore them.

Saved us a lot of those Sighs! :-)Just an idea to save some bandwidth for you and your customers. :-)

...the majority is always wrong, and always the last to know about it...

  • Comment on Re^2: Monitoring an FTP upload directory

Replies are listed 'Best First'.
Re^3: Monitoring an FTP upload directory
by friedo (Prior) on Nov 08, 2006 at 00:29 UTC

    I think this is a great idea, thanks. I'm going to go with tailing the xferlog, too. (Why didn't I think of that before? :) ).

Re^3: Monitoring an FTP upload directory
by shenme (Priest) on Nov 08, 2006 at 02:48 UTC
    I've really wanted to do this, like creating a <your_filename>.received_correctly_and_processed.txt file. Automatically removing the file after a while makes it sound even better.

    The problem we often saw was that we were _so_ fast at picking and moving the file, that the user wouldn't ever see it, even when directly following the PUT with a DIR. It is one thing to see the transition from 'there' to "not there", but it kinda freaked them out that they never saw it at all. Like it had gone into the bit bucket. And our applications are named _somewhat_ differently...

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://582735]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2022-11-27 02:51 GMT
Find Nodes?
    Voting Booth?