Ryan Lortie abbb225738 inotify: don't assume mainloop is running ... GFileMonitor takes great care to sample the thread-default main context at the time that it is created in order that events can be dispatched to the correct thread when they come in. The inotify GFileMonitor implementation uses a global file descriptor shared between all watches. It has to poll this file descriptor from somewhere so it arbitrarily picks the default main context. The problem with that is that the user might not be running it. Let's use the GLib worker thread for this instead. It's guaranteed to be running if you need it, and this is exactly the sort of problem it was meant to solve. https://bugzilla.gnome.org/show_bug.cgi?id=704873		2013-07-28 17:19:38 -04:00
..
ginotifydirectorymonitor.c	gio + inotify support for hard links	2012-12-19 08:19:18 -05:00
ginotifydirectorymonitor.h	Clean up improper #includes	2010-08-06 13:05:18 -04:00
ginotifyfilemonitor.c	inotify: fix compile	2012-12-19 09:10:12 -05:00
ginotifyfilemonitor.h	Removed unnecessary file	2007-11-28 16:01:59 +00:00
inotify-helper.c	Remove a few more G_GNUC_INTERNAL users	2013-01-18 13:28:43 -05:00
inotify-helper.h	gio/ docs/reference/gio Merged gio-standalone into glib.	2007-11-26 16:13:05 +00:00
inotify-kernel.c	inotify: don't assume mainloop is running	2013-07-28 17:19:38 -04:00
inotify-kernel.h	Send CHANGES_DONE_HINT on file moves if no IN_CLOSE_WRITE is emitted	2011-12-05 18:27:34 +00:00
inotify-missing.c	inotify: don't assume mainloop is running	2013-07-28 17:19:38 -04:00
inotify-missing.h	gio/ docs/reference/gio Merged gio-standalone into glib.	2007-11-26 16:13:05 +00:00
inotify-path.c	inotify: fix a memleak	2013-01-21 09:51:09 -05:00
inotify-path.h	gio + inotify support for hard links	2012-12-19 08:19:18 -05:00
inotify-sub.c	gio + inotify support for hard links	2012-12-19 08:19:18 -05:00
inotify-sub.h	gio + inotify support for hard links	2012-12-19 08:19:18 -05:00
Makefile.am	Rework the build system for a new tests approach	2013-05-31 23:12:15 -04:00