See attached a re-post from Mono-osx list. The issue is about
FileSystemWatcher rarely noticing file changes. What might be the
cause thereof?
Earlier I was told not to monitor an SMB share because it were
implemented using a polling approach for remote shares so instead I
connected a Windows drive to an OS X SMB share, monitoring the local
changes there. However the same results occurred last time I checked
running the DOS app locally on OS X, so without any SMB in between,
so that the latter probably isn't the source of the problem... Also,
the same issue occurs when my Mono application performs the changes
itself, so I doubt it's an issue with the DOS application performing
the changes.
Has anyone got this working on OS X? Any hints on how to debug this?
Thank you,
Andreas
Anfang der weitergeleiteten E-Mail:
Von: Andreas Färber <[EMAIL PROTECTED]>
Datum: 5. Dezember 2006 22:58:48 MEZ
An: Mono OSX List <[EMAIL PROTECTED]>
Betreff: [Mono-osx] FileSystemWatcher
Hello,
Are there any known issues using FileSystemWatcher on OS X? (v10.4.8,
Mono 1.2.1 preview)
I have an object model where some objects have their own watcher to
monitor a single file. The instances are set up like this:
fsw = new FileSystemWatcher(dir, file);
fsw.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.Size;
fsw.Changed += ...
fsw.EnableRaisingEvents = true;
Yet they rarely notice file changes. The files are on the local HFS+
volume and are either manipulated via SMB or through the app itself.
From time to time my app also crashes on startup with a SIGABRT in
FileSystemWatcher:get_MangledFilter (called
from :set_EnableRaisingEvents).
Any ideas?
Andreas
_______________________________________________
Mono-osx mailing list
[EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/mono-osx
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
