[Mono-bugs] [Bug 354701] Add a way to disable FileSystemWatcher for ASP.NET apps

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Jan 18 08:14:02 EST 2008


User informatique.internet at fiducial.fr added comment

--- Comment #3 from Hubert FONGARNAND <informatique.internet at fiducial.fr>  2008-01-18 06:14:02 MST ---
Thanks for your answer

(In reply to comment #2 from Marek Habersack)
> Hey Hubert,
> On one hand, I don't mind such a mechanism to turn off the managed filesystem
> watcher. On the other, turning FSW off severely cripples the ASP.NET
> functionality - no auto-recompile, no auto-restart on updates. It might have
> serious consequences in some cases. Granted, turning the behavior on would be a
> conscious decision and we could make sure the consequences are known. 

If you use ASP.NET over NFS, today, there's no other way to manually restart
mod-mono-server's if a file has changed (we already do that). I agree that this
behaviour should not be the default one, and would be a conscious decision

> The next question is - where should it be implemented and how exactly. Whether
> it should be a System.Web local mechanism to disable creating FSW instances at
> all? 

I think this solution is better, because if someone, want (in the program, and
not in System.web classes) use a FileSystemWatcher it should work...

Or should it rather be in the System.IO.FileSystemWatcher class which,
> when the mechanism is on, should silently ignore requests? How - should it
> disable all the watchers or just the managed one, should none of the
> non-managed be absent?

-> may be creating a "FakeFileSystemWatcher" that doesn't watch anything?

> Also, have you tried installing gamin or fam? Maybe that would be the solution
> to this issue for you? FSW looks for the following watcher implementations, in
> order given:
> 1. inotify
> 2. gamin
> 3. fam
> 4. managed

-> I've installed gamin and fam and tried to use them, but the version included
with RHEL4 are not compatible with mono.
-> I've read that gamin and fam are buggy when used with old dnotify API...

> I'm open for discussion and input from you - if you can, please test gamin/fam
> first, though.

I've forced to use gamin by forcing mode... It says that mono can't find the
FamNextEvent symbol in the library

and i've read on the web that gamin and fam RHEL4 version are too old for
> regards

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list