From e0dddff176a01d410904b6750b3395de4f7e54db Mon Sep 17 00:00:00 2001 From: Lukasz Kasprzak Date: Mon, 14 Sep 2026 21:39:00 +0200 Subject: plan 9: keyword cache keys on extension, max-read and Unicode tables, trims removed keywords --- man/krino.conf.5 | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) (limited to 'man') diff --git a/man/krino.conf.5 b/man/krino.conf.5 index cd16ada..b00967a 100644 --- a/man/krino.conf.5 +++ b/man/krino.conf.5 @@ -529,9 +529,10 @@ records in which of the directory's content keywords the text contains, and answers later content tests from it while the file is unchanged. No text and no file names are stored; a file is known by device, inode, -size and modification time, which a move or rename within one filesystem +size, modification time and extension, which a move within one filesystem keeps. -The keywords are stored as written in the configuration. +The keywords are stored normalised, the way the test compares them, and +only those the directory still uses. .Pp A file is extracted again when it changes, or when a test asks about a keyword its entry was never checked against. @@ -539,10 +540,15 @@ Failures are never cached, and a file above .Ic max-read is refused before the cache is read. The whole cache is discarded when an extraction tool is installed, removed -or replaced, or when krino's extraction or normalisation changes. +or replaced, when krino's extraction or normalisation, the Go release or the +Unicode tables change, or when the directory's +.Ic max-read +changes. Each run keeps entries only for files still in the directory. A file edited in place with its size and modification time preserved keeps -its old answers; deleting the cache resets everything. +its old answers, as does a new file reusing a deleted file's inode with the +same size, extension and preserved modification time; deleting the cache +resets everything. .Sh ACTIONS .Ss Chains A file's chain is the actions of every matching rule, in rule order, and -- cgit v1.3