Warning I: this project is in early development stage, you might not find it useful for now. It only works in Linux (2.6+) boxes (as it depends on
libnotify to do most of the work).
Most of this lib is a wrapper around
EventEmitter tied on.
$ npm install hey
var Hey = Hey;var watch =path : '/path/to/something'recursive : true | falsemask : HeyFLAGSDELETE | HeyFLAGS...;watch;watch;
Hey constructor takes an object as parameter, and it contains the following keys:
path: the path to watch (required, obviously);
recursive: in the case the path you choose is a folder, you can choose to watch it recursively. Optional, default not set;
mask: the mask to listen to. Ex. if you want just to watch for new files, you use only
Hey.FLAGS.CREATEas mask. All available masks (for
libnotify) are listed in this document; Optional, default to
Hey.FLAGS.MODIFY | Hey.FLAGS.CREATE | Hey.FLAGS.DELETE | Hey.FLAGS.SELF_DELETE | Hey.FLAGS.MOVE | Hey.FLAGS.SELF_MOVE;
Warning II: activating
recursive in a folder, you may run out of buffer (as it supports 1024 listeners). We do not plan to change this now as it required, on Linux, changing the
ulimit fopen size and the source code of
The following events are available for use (but, most of them only works with folders):
EOB: fired when all available listeners are taken; perhaps you're watching too many files?
FB: fired when some listener becomes available; it means Free Buffer, not the social thing;
any: fired when any path event occurs (except
access: fired when a file is accessed;
modify: fired when a file is modified;
open: fired when a file is opened;
close: fired when a file is closed;
metadata: fired when the path attributes are modified;
create: fired when a path is created;
delete: fired when a path is deleted;
self delete: fired when the
pathfrom constructor is deleted;
self move: fired when the
pathfrom constructor is moved;
move: fired when a path is moved;
ignore: fired when an event is ignored (this event could happen if you use your own
unknown: fired when an unknown event happens to a path (not really unknown, but not relevant to the moment IMHO).
The callback function can receive three arguments:
path: the path which triggered the event;
type: fow now, if the path is a file
mask: the mask of the event (number).
Warning III: these parameters works for all events except for
FB, which receives none.
Hey in my home folder (ext4 fs) recursively, which have around 210G of data, around 41157 folders and 484730 files. When started, the CPU usage goes to ~30% (Core i7) and memory usage to ~180M. When the "first round" of processing is done (read the folder recursively), CPU usage goes to 0% and memory usage to ~80M; and I couldn't detect any leaks so far, as it's runtime was about 6 hours. Of course, more testing needs to be done, specially if the number of notifiers increase.
Note: using default
ulimit fopen in 1024.
Our plan is to support all platforms in the future, as Node's
fs.watch() evolves (seriously, do this kind of work on what it is now would be insane).
Copyright (C) 2012 Humantech Gestao do Conhecimento
Distributed under the MIT License, the same as NodeJS.
Read this if you're in doubt.