David Roundy
David Roundy
Yes, but could the file be generated dynamically? On the other hand, perhaps it would be disingenuous to support static linking of a tool that doesn't work with statically linked...
Yes, it's definitely doable. I might be tempted to put it in ~/.cache/fsatrace/, so it would seldom need to be replaced, and you avoid the dangers of working with /tmp/....
The "at" variants of functions are wonderful system calls, and it seems well worth supporting them! (And they aren't that hard. Here is how I do it in bigbro: https://github.com/droundy/bigbro/blob/master/linux-proc.h#L3
I'll add mention that a path name based API had the disadvantage of making it impossible to create a posix compliant (aka correct) file system. Unless you do not, for...
I want to qualify what I wrote about a path name based API. Such an API can (I think) be entirely safe, if you force the use of the "fh"...
I'd like to add that I have a use case where a single datalist is used for several list inputs. I presume this would also be broken? It's a long...
@sezna can you share where your fork is?
I'd appreciate this on the next major version bump.
You need more than just those six syscalls to for tracing file accesses, you also need to handle openat, unlinkat, truncate, utime, utimes, futimesat, lstat, lstat64, readlink, readlinkat, stat, stat64,...
Hi Jason, I hadn't thought to compare timings of libbigbro with strace, since I never considered using strace. I've just now run a couple of timings compiling SDL2, which happened...