On 11/22/2010 10:44 AM, Andy Levy wrote:
> On Mon, Nov 22, 2010 at 11:36, Ludwig, Michael
> <Michael.Ludwig_at_delphi-mb.de> wrote:
>>> From: Andrey Repin
>>> Sent: Monday, November 22, 2010 5:11 PM
>>
>>>> Any ideas of any software that can handle this.
>>>
>>> You'd be surprised, but the very filesystem (in Unix/Linux at
>>> least) support
>>> trigger mechanism. All you need is to write appropriate filter.
>>
>> I think one such mechanism for Linux is called inotify.
>>
>> There should be similar facilities for Windows.
>
> System.IO.FileSystemWatcher in the .NET Framework.
> http://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher.aspx
>
> FSEvents on MacOS X 10.5 and up.
>
>> Of course, there is a low-level API, but I'm thinking of
>> something that allows you to write:
>>
>> OnCreateFile: call somescript.cmd
>> OnCreateDir: perl someperl.pl
>>
>> The generic name should be *file system event monitor*.
>> But I haven't used any.
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).
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-11-22 18:12:33 CET