fseventer ¬
v2.6.5, July 2008 -- http://www.fernlightning.com/

Description
	•	Observes filesystem changes using the same underlying API as Spotlight.
	•	Provides a graphical representation of the file activity.
	•	Example use could be to determine what files are be changed via installation, preferences, etc.
	•	Requires root access & will only work on Mac OS X 10.4+

Known Issues
	•	First time it is run it will ask for the admin password so that it can set root permissions on it's internal 
		helper tools (fetool - a version of gfslogger, leotool - FSEvents monitor)
	•	It must be copied to a volume where root permissions can be set, i.e. the boot volume!
	
Release Notes
	•	2.6.5
	⁃	Missing events bug fix (some events were quietly being ignored)
	⁃	Cosmetic improvements - crisper icons in table, core animation in filter
	⁃	Help now comments on Apple's fseventd (which has nothing to do with this app), and uninstalling
	•	2.6.2 - Minor Bug fixes - removed noisy debug code
	•	2.6 - Filtering version
	⁃	Advanced filters (event, process, path, etc) can be applied to all views
	⁃	Unified functionality into toolbar, with some nicer icons
	⁃	Extra preference added to revert to old style of tree
	•	2.5 - Interface Redux
	⁃	Improved layout and clarity of tree
	⁃	Fixed printing bug and various other minor bugs
	•	2.2.2
	⁃	Usability bug fix  - donate window will NOT show once you've checked the donate box
	⁃	Sparkle update fix - (removes need to force-quit application to complete auto-update)
	•	2.2 - Bug fixes, sparkle updating support
	•	2.1 - Leopard release:
	⁃	Can monitor leopard FSEvents.

There is one major caveat to be concerned with (from kernelthread.com):

[where fseventer uses a version of fslogger]

The interface that fslogger uses is private to Apple.  Currently, there is a
caveat regarding the use of this interface by third parties (including
fslogger).  While the change notification interface  supports multiple clients, 
there is a single kernel buffer for holding events that are to be delivered to
one or more subscribers, with the primary subscriber being Spotlight.  Now, 
the kernel must hold events until it has notified all subscribers that are 
interested in them.  Since there is a single buffer, a slow subscriber can 
cause it to overflow.  If this happens, events will be dropped for all 
subscribers, including Spotlight.  Consequently, Spotlight may need to look 
at the entire volume to determine "what changed".

fslogger is meant to be a learning tool.  If you use it, you must understand
the aforementioned caveat.  If you cause heavy enough file system activity 
(what's "heavy" will vary greatly, depending on your system and its currently 
available resources), both fslogger and Spotlight may miss events, causing 
Spotlight to spend some extra time looking at your volume.  Note that Spotlight 
will not reindex the entire volume‚ it will only look for the changes that 
it missed.

An example of a typically heavy file system activity (that may quite possibly 
cause events to be  dropped) is unpacking a giant tarball.  Finally, if events 
are missed, fslogger will indicate that event (missing events is an event 
itself).