566 B
566 B
<html lang="en">
<head>
</head>
</html>
Hacking filekäfer
Checkpointing
Thanks to @lusis for the suggestion on a good path for tracking offsets in files as filekäfer reads and processe.
Basically we need to track:
-
Bytes read
-
The inode number of the file
-
Filesize
For cases of a copytruncate, filekäfer can check if the overall filesize is greater than the last read, and if so, assume that the offset in the file has been reset.