I am aware that there are platform-specific issues with watching files.
But I am getting strange-bad results just on Linux. Please tell me I am
doing something silly below.
var fs = require('fs');
function act(curr, prev) {
console.log('the current mtime is: ' + curr.mtime);
console.log('the previous mtime was: ' + prev.mtime);
};
function act2(event,file) {
console.log('event is: ' + event);
if (file) {
console.log('filename provided: ' + file);
} else {
console.log('filename not provided');
}
};
// ucomment one or the other (but not both!) of the following lines:
// fs.watchFile('test.txt', act);
// fs.watch('test.txt', act2);
When I use fs.watch + act2, and simply repeatedly 'touch' the file (about
once per second) the first two events are 'change' and the next three are
'rename' (!) and then program just stops producing output. It's as if the
events are eitehr never fired or never handled. I understand that this is
based (on Linux) on inotify?
So I switch to fs.watchFile + act. Again, I 'touch' the test file about
once per second. This always produces an event. The problem is, about 30%
of the time one touch produces two events! And about 5% of the time, one
touch produces three events! I understand that this is actually a polling
solution, and...
My own naive polling code does not have these problems. At least it does
not seem to.
I need the action to run reliably (which seems to eliminate fs.watch) and
exactly once (which seems to eliminate fs.watchFile) so it seems I am stuck
with my own clunky polling solution. Again: Am I doing something silly?
Thanks!
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
