On Mon, Nov 22, 2010 at 9:55 PM, Andrey Repin <anrdae...@freemail.ru> wrote: > Greetings, Les Mikesell! > >> Realistically, you probably don't need to kick off the job the instant >> the filesystem changes - you'll at least want to wait until the file >> transfer completes. I'd expect a scheduled job running from cron on >> linux or the windows task scheduler checking for new files every few >> minutes to work at least as well as your existing manual process and >> avoid any OS/filesystem dependencies (i.e. it could run from linux >> checking a smb/cifs mounted windows filesystem or the reverse if you want). > > Cron job won't be able to know if file transfer is completed. It will have to > guess from, e.g., testing the archive (if it's archive) for integrity. > filesystem notification mechanism will for sure know, when the iostream got > filewriteclose event.
One of the more helpful tricks is to check if it's newer than a certain period, and *older* than a certtain, modest period (such as a few minutes) to make sure the transfer is complete.
