jacereda
jacereda
I don't think it would be problematic in my scenarios. To trace an operation, traced-fs would mount a T: drive that mirrors C: and the build system would need to...
Well, maybe having it permanently mounted is desirable keeping in mind that mounting and unmounting will probably hurt caching.
@droundy Could you make a quick test with your NFS setup? Something like this would suffice: ``` make ./fs & ls -l traced/ & cat traced/.ops/$! ```
Sorry, I edited the command sequence afterwards, can you recheck?
Try this: ``` killall fs & ls -l traced/ & cat traced/.ops/$! ``` The killall will fail if some process is running inside the `traced` directory, so make sure you...
Good, seems to work properly. Thanks.
After fixing a bug in utimens handling, I can trace a `stack build`. That was failing miserably with `fsatrace`.
If this happens at some point I guess it could be an alternative to dokany: https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13522845-add-fuse-filesystem-in-userspace-support-in-wsl
I've been reconsidering the traced-fs implementation for Windows. I have a prototype using dokany but I think it would be just easier and more stable to write a minifilter driver....
Would it require a separate operation type or is a 'read' of the directory enough?