Hi, Quoting Jakub Wilk (2016-05-30 13:08:47) > * Johannes Schauer <josch@debian.org>, 2016-05-28, 10:04: > >I was investigating this problem last year and as far as my research > >went, there is no tracing method in existence which reliably traces > >system calls in general, file system access or read/write operations > >while keeping track of the acting pid that is 100% reliable. The > >methods I found either were not transparent (and would thus break test > >suites) or suffered from race conditions where it was possible to > >register an operation but miss the pid the operation was carried out by > >or dropped operations if they occurred with a too-high frequency... > > Have you tried systemtap? yes, and it will drop events if they arrive too fast. There is no way to completely prevent it from doing so. One can only increase queue and buffer sizes and timeouts but that will never provide 100% reliability. cheers, josch
Attachment:
signature.asc
Description: signature