71–80 of 80 posts
Earlier quoted context omitted.
Wait, it doesnt hook the OS file handling routines? it actually manually rescans the filesystem?
It does one or the other. There are concerns about OS filesystem event hooks. The current solution isn’t ideal, and is being addressed here: https://github.com/e-dant/watcher/issues/10
Looking at Win32, it scans the whole directory periodically, right? I must miss something, but how can that be called efficient?
It’s efficient because it beats kqueue while reporting events accurately. A proper benchmarking program is in the works, however manual testing does show only minimal resource usage. For more, see this issue: https://github.com/e-dant/watcher/issues/10
When I last tried to implement this, by far the toughest part was making sure the file that’s been newly detected is done being written to. On ntfs I couldn’t find a good technique, even last modified time was not reliable. I had to watch it for changes myself.
I have personally written a similar tool and I am very curious about how this could be using a near-zero amount of resources while maintaining accuracy. As far as I know, there are two ways to implement this functionality: 1) store an in memory representation of the file system and periodically refresh the in memory state by polling the paths under watch and emitting events when differences are detected 2) hook into…
More technically, here’s what we have: A “baseline” filesystem watcher which uses only the standard library. It has been made to beat kqueue. And it does. A platform filesystem watcher for Darwin is used, but certain event properties are handled by the standard library. Namely, the event time and the path type. A platform filesystem watcher is schedule for Windows. Work hasn’t been started. A platform filesystem watc…
Is there a well-tested, reliable, flexible and good working tool for windows that does the same and can be installed as a service? Just watch a directory and do something that I can configure easily with a textfile?
This one looks interesting: https://github.com/emcrisostomo/fswatch
Earlier quoted context omitted.
Never even thought of that; I don’t know. I assumed it was when a write was done. Whatever that means, I don’t know either.
Would this mean that fs event based antivirus scanners could be side-stepped by writing a payload to a file and then never closing the handler?
Does it keep working when files get overwritten by moving another over it, like some Linux text editors do?
I should test this. I haven’t seen a problem with that so far in my personal usage, so I’m inclined to say probably. That’s a good test case. I’ll make an issue.
Earlier quoted context omitted.
No, its a certificate issue; probably minor, but a server-side thing to attend to by the looks of it.
There are no certificate issues in my Chrome. Are you sure your not on some MITMing VPN?