Directory Monitor

Just to clarify what directory monitor actually does

Directory monitor reacts to windows file system events

Such as

File creation (Added)
Deletion (Removed)
ETC

Let talk about File creation

File creation is just file creation and nothing else

You can have the following situation.

1 File is created and it is open for writing
2 Data is written into the file.
3 File is closed

The event fires at step number 1 and our software then wait until the file is closed and then submit the package for execution.

Or the software (FTP client, FTP server, explorer) may create an empty file to check if the remote directory actually writable
It does happen quite often.


1 File is created
2 File is deleted.
3 File is created and it is open for writing
4 Data is written into the file.
5 File is closed

What we can do we can add an option to ignore empty files.
That however does not mean that it will help in your case.

Also

"If you notice, even if the tmp file did come in, it has an extension of .tmp and the pattern is for *.csv. so at the very least it still should have ignored the *.tmp until it became .csv"

In this case, you should monitor for "Rename event", and not "Add file event"

Thanks Mike. yes, understand all of that and how the monitor works as I have used the Windows API directly myself in a small way in the past. In your implementation is the filename filter used at detection time or after?

I ask because in our case I would still believe that only a single Event should be registered because even though I can see the client side FTP PUT a file with an extension of .TMP and then within milliseconds FTP MOVE the file to - there is still only a single .CSV file created.

We are only monitoring for *.csv yet we get 2 Execution Log Event entries and as you say this method of 'testing' the server before commiting the final file is common. However, in this scenario if the filename filtering kicked in during the 'watching' I would have through we would still only get a single Event being created rather than 2.

Also, whilst I appreciate the offer of ignoring zero sized file I would thinks this could be problematic for your other clients and also in this case the file actually seems to not be zero for very long

Hi

Just want to add that I have the following methods to try and troubleshoot and in ALL cases 2 files events are created. The first tow methods were purposely done to hopefully avoid any chance of 2 files being created.

1. On the SERVER Drag & Drop file from Windows Explorer from a samples folder to the SHARE open in another window. This is totally under my control and there is NO temporary file initially created and I am not doing any probing to see if the file or directory pre-exist.

2. On the SERVER COPY&Paste from Windows Explorer from a samples folder to the SHARE open in another window. This is totally under my control and there is NO temporary file initially created and I am not doing any probing to see if the file or directory pre-exist.

3. On my Dev Workstation open up WinSCP and connect to the FTP Home as if I was the external client. DRAG&DROP the sample file from Windows Explorer to the WinSCP File Area. This generates a PUT of a file with .TMP extension and a MOVE of that file to the CSV extension. WinSCP must be doing this.

Here is the gentleman who is having similar problems to yours.

forum.powerbasic.com/forum/user-to-user-...enotification-double

We are still not able to reproduce the problem I think the only way for us to do so is to buy the same NAS storage as yours

I after spending so much time reading about problems with writing file system monitors my conclusion that API created by Microsoft is not 100% reliable.

It does apply to both local folders and network shares.

We will create a special build of a directory monitor for you and provide you with the link.

Again there is no 100 per cent guarantee that we will be able to fix the problem

Thanks for the fix in v6.3.7.16

cheers