Quote:
Originally Posted by
Annihilannic
1) Each time you process the directory, touch a flag file. Then use find /pathname -newer /path/to/flagfile. Doesn't really save you the overhead of running find but saves you having to do comparisons.
The problem with that is files dragged from Windows don't always update the time stamp on the file(s) being transferred. I've tried using the atime, mtime, and ctime of the files, none of which would work 100% of the time.
Quote:
2) Does vsftpd keep the file open for the entire duration of the transfer? If so you could use fuser on the file until it shows no processes accessing it, and then assume that the upload is complete. Normally the best way is to upload files to a temporary name and then rename them when complete, but that requires end-user actions which probably aren't appropriate in your situation.
Now that's a good question. I don't know, didn't even think of it, but I can check on it. Thanks!
Quote:
I'm kind of surprised though that vsftpd doesn't log an upload complete event, even at a not very verbose level?
vsftpd does log when the transfer is complete. But we have users that will transfer 5 - 15 files at times. I don't really want a notification for each file, just one when the lot is complete. So for now when it sees a complete transfer with sleeps for 15 seconds, checks the filesystem size for changes, if yes waits for the next transfer to complete, if not, send the email.
Quote:
Incidentally, if you are prepared to consider a commercial product, Tumbleweed's SecureTransport is a good product for doing most of what you describe... i.e. triggered actions based on incoming files, etc.
I've not heard of Tumbleweed, nor been able to find much of anything like what I'm doing. Thanks! I'll check it out, but I know the company won't spring for it until the economy picks up. I am in an auto related field.
Thanks a bunch!