https://bugzilla.novell.com/show_bug.cgi?id=354701
User [EMAIL PROTECTED] added comment https://bugzilla.novell.com/show_bug.cgi?id=354701#c2 --- Comment #2 from Marek Habersack <[EMAIL PROTECTED]> 2008-01-18 04:44:49 MST --- 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. 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? 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? 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'm open for discussion and input from you - if you can, please test gamin/fam first, though. 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. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
